Horton

Re: [DOC] Add detail regarding resource consumption wrt max_connections

reid.thompson@crunchydata.com

View thread
From: reid.thompson@crunchydata.com
To: Roberto Mello <roberto.mello@gmail.com>, Cary Huang <cary.huang@highgo.ca>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-01-22T13:58:23Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Document that increasing max_connections uses more resources.

On Fri, 2024-01-19 at 17:37 -0500, reid.thompson@crunchydata.com wrote:
> On Sat, 2024-01-13 at 10:31 -0700, Roberto Mello wrote:
> > 
> > I can add a suggestion for the user to consider increasing
> > shared_buffers in accordance with higher max_connections, but it
> > would be better if there was a "rule of thumb" guideline to go
> > along. I'm open to suggestions.
> > 
> > I can revise with a similar warning in max_prepared_xacts as well.
> > 
> > Sincerely,
> > 
> > Roberto
> 
> Can a "close enough" rule of thumb be calculated from:
> postgresql.conf -> log_min_messages = debug3
> 
> start postgresql with varying max_connections to get
> CreateSharedMemoryAndSemaphores() sizes to generate a rough equation
> 

or maybe it would be sufficient to advise to set log_min_messages =
debug3 on a test DB and start/stop it with varying values of
max_connections and look at the differing values in 
DEBUG: invoking IpcMemoryCreate(size=...) log messages for themselves.