Parameters - Nearbase

Overview

The Parameters tab on your instance detail page shows the PostgreSQL configuration parameters currently applied to your database. These are the settings that control memory allocation, query planning, connection limits, logging thresholds, and more.

Viewing Parameters

Open the instance in the console.
Go to the Parameters tab.
You’ll see the full list of parameters with their current running values.

Running vs. Pending Parameters

Some parameter changes take effect immediately; others require a database restart.

State	Description
Running	The value currently active on the database process.
Pending	A value has been submitted but not yet applied. This appears when a parameter requires a restart to take effect.

When a parameter is in Pending state, the new value will be applied at the next scheduled maintenance window or when you manually restart the instance.

Common Parameters

Parameter	Description
`max_connections`	Maximum number of simultaneous client connections.
`shared_buffers`	Amount of memory dedicated to PostgreSQL’s shared buffer cache.
`work_mem`	Memory available for each sort or hash operation per query.
`log_min_duration_statement`	Queries slower than this threshold (in ms) are written to slow query logs. Set to `-1` to disable.
`idle_in_transaction_session_timeout`	Automatically terminates sessions that have been idle in a transaction for longer than this duration.
`statement_timeout`	Automatically cancels queries that run longer than this duration.
`timezone`	The time zone used for timestamps in this database.

Parameter modifications are available on request. Contact team@m.nearbase.dev if you need to tune a specific parameter for your workload.

Slow Query Threshold

The log_min_duration_statement parameter controls what appears in your Slow Query Logs. By default it is set to capture queries that take longer than a few hundred milliseconds. Lowering this value captures more queries but increases log volume.