How to fix Configuration limit exceeded in PostgreSQL

ERROR: index row size 4496 exceeds maximum 2712
ERROR: row is too big: size 8192, maximum size 8160
ERROR: stack depth limit exceeded

-- Move rarely-accessed columns to a separate table
CREATE TABLE users_extended (
  user_id INTEGER REFERENCES users(id),
  profile_data TEXT,
  preferences JSONB
);

-- Query across tables when needed
SELECT u.*, ue.profile_data FROM users u
LEFT JOIN users_extended ue ON u.id = ue.user_id;

-- Problem: Indexing large text column
CREATE INDEX idx_large_text ON documents(body); -- May fail

-- Solution 1: Hash the value
CREATE INDEX idx_body_hash ON documents(md5(body));

-- Solution 2: Use full-text search index (more efficient)
CREATE INDEX idx_body_fts ON documents USING GIN(to_tsvector('english', body));

-- Query with full-text search
SELECT * FROM documents 
WHERE to_tsvector('english', body) @@ to_tsquery('english', 'your:query');

-- Problem: Deep recursion
CREATE OR REPLACE FUNCTION find_children(id INT) RETURNS TABLE(child_id INT) AS $$
BEGIN
  RETURN QUERY SELECT child_id FROM items WHERE parent_id = id;
  RETURN QUERY SELECT * FROM find_children(child_id);
END;
$$ LANGUAGE plpgsql;

-- Solution: Use WITH RECURSIVE CTE
WITH RECURSIVE hierarchy AS (
  SELECT id, parent_id FROM items WHERE parent_id = $1
  UNION ALL
  SELECT i.id, i.parent_id FROM items i
  INNER JOIN hierarchy h ON i.parent_id = h.id
)
SELECT id FROM hierarchy;

-- Problem: Too many grouping sets
SELECT col1, col2, col3, col4, COUNT(*)
FROM table1
GROUP BY GROUPING SETS (
  (col1, col2, col3, col4),
  (col1, col2, col3),
  (col1, col2),
  (col1),
  ()
);

-- Solution: Separate simpler queries
SELECT col1, col2, col3, col4, COUNT(*) FROM table1
GROUP BY col1, col2, col3, col4
UNION ALL
SELECT col1, col2, col3, NULL, COUNT(*) FROM table1
GROUP BY col1, col2, col3;