Supabase Postgres Best Practices Skill 安全审计

2425**Correct (automatic cleanup of idle connections):**2627```sql28-- Terminate connections idle in transaction after 30 seconds29alter system set idle_in_transaction_session_timeout = '30s';3031-- Terminate completely idle connections after 10 minutes32alter system set idle_session_timeout = '10min';3334-- Reload configuration35select pg_reload_conf();36```

2name: supabase-postgres-best-practices3description: "Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query."4license: MIT

2728-- Create policy for users to see only their orders29create policy orders_user_policy on orders30  for all31  using (user_id = current_setting('app.current_user_id')::bigint);3233-- Force RLS even for table owners34alter table orders force row level security;3536-- Set user context and query37set app.current_user_id = '123';38select * from orders;  -- Only returns orders for user 12339```

2name: supabase-postgres-best-practices3description: "Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query."4license: MIT

3637For all constraint types:3839```sql40-- Check constraints41do $$42begin43  if not exists (44    select 1 from pg_constraint45    where conname = 'check_age_positive'46  ) then47    alter table users add constraint check_age_positive check (age > 0);48  end if;49end $$;5051-- Foreign keys52do $$53begin54  if not exists (55    select 1 from pg_constraint56    where conname = 'profiles_birthchart_id_fkey'57  ) then58    alter table profiles59    add constraint profiles_birthchart_id_fkey60    foreign key (birthchart_id) references birthcharts(id);61  end if;62end $$;63```