Supabase Update Project Postgres Config

Updates specified PostgreSQL configuration parameters for an existing Supabase project (`ref`) to optimize database performance; note that unspecified parameters remain unchanged, and caution is advised as incorrect settings can impact stability or require a restart.

मूल्य

मुफ़्त Action

एकीकृत भुगतान

अभी समर्थित नहीं

• refstring

  आवश्यक
  The unique reference ID of the Supabase project.
• work_memstring
  Memory for internal sorts and hash tables before writing to temp disk files (e.g., '4MB', '64MB').
• max_wal_sizestring
  WAL size that triggers a checkpoint (e.g., '1GB', '2048MB').
• wal_keep_sizestring
  Minimum size of past WAL log segments in pg_wal for standby servers (e.g., '128MB', '512MB'); replaces older wal_keep_segments.
• shared_buffersstring
  Memory for shared memory buffers (e.g., '128MB', '1GB').
• max_connectionsinteger
  Maximum concurrent database connections. Typically between 1 and 262143.
• statement_timeoutstring
  Maximum allowed duration for any SQL statement (e.g., '10000ms', '30s'); '0' typically disables timeout.
• effective_cache_sizestring
  Estimated disk cache size for a single query (e.g., '4GB', '512MB').
• maintenance_work_memstring
  Maximum memory for maintenance operations like VACUUM, CREATE INDEX (e.g., '64MB', '1GB').
• max_parallel_workersinteger
  Maximum workers the system can support for parallel queries. Typically between 0 and 1024.
• max_worker_processesinteger
  Maximum background processes the system can support. Typically between 0 and 262143.
• max_slot_wal_keep_sizestring
  Maximum WAL file size replication slots can retain in pg_wal (e.g., '1GB', '512MB'). '0' might mean unlimited; check PostgreSQL docs.

• data

  आवश्यक
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  आवश्यक
  Whether or not the action execution was successful or not

अभी कोई सत्यापित संबंधित उपयोग मामला लिंक नहीं है।