Re: [DOC] Add detail regarding resource consumption wrt max_connections - Mailing list pgsql-hackers

From reid.thompson@crunchydata.com
Subject Re: [DOC] Add detail regarding resource consumption wrt max_connections
Date
Msg-id 2c9d3664ff7adc506191f92db031543925abe0df.camel@crunchydata.com
Whole thread Raw
In response to Re: [DOC] Add detail regarding resource consumption wrt max_connections  (reid.thompson@crunchydata.com)
Responses Re: [DOC] Add detail regarding resource consumption wrt max_connections
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Move walreceiver state assignment (to WALRCV_STREAMING) in WalReceiverMain()
Next
From: Aleksander Alekseev
Date:
Subject: Re: Remove unused fields in ReorderBufferTupleBuf