public inbox for [email protected]
help / color / mirror / Atom feedFrom: Roberto Mello <[email protected]>
To: Cary Huang <[email protected]>
Cc: [email protected]
Subject: Re: [DOC] Add detail regarding resource consumption wrt max_connections
Date: Sat, 13 Jan 2024 10:31:42 -0700
Message-ID: <CAKz==bLJAwDGMMRqJSwA0Y+h10OYff73cd1pNCyzGnwYLq74BA@mail.gmail.com> (raw)
In-Reply-To: <170509767861.1131.15083983626399995184.pgcf@coridan.postgresql.org>
References: <CAKz==bJBCWrvN77fmuZ2XqD3jazWEb=E80AA4Yv9C9tQ61YDdQ@mail.gmail.com>
<170509767861.1131.15083983626399995184.pgcf@coridan.postgresql.org>
On Fri, Jan 12, 2024 at 3:15 PM Cary Huang <[email protected]> wrote:
> I think it is good to warn the user about the increased allocation of
> memory for certain parameters so that they do not abuse it by setting it to
> a huge number without knowing the consequences.
>
> It is true that max_connections can increase the size of proc array and
> other resources, which are allocated in the shared buffer, which also means
> less shared buffer to perform regular data operations. I am sure this is
> not the only parameter that affects the memory allocation.
> "max_prepared_xacts" can also affect the shared memory allocation too so
> the same warning message applies here as well. Maybe there are other
> parameters with similar effects.
>
> Instead of stating that higher max_connections results in higher
> allocation, It may be better to tell the user that if the value needs to be
> set much higher, consider increasing the "shared_buffers" setting as well.
>
Appreciate the review, Cary.
My goal was to inform the reader that there are implications to setting
max_connections higher. I've personally seen a user mindlessly set this to
50k connections, unaware it would cause unintended consequences.
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
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: [DOC] Add detail regarding resource consumption wrt max_connections
In-Reply-To: <CAKz==bLJAwDGMMRqJSwA0Y+h10OYff73cd1pNCyzGnwYLq74BA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox