Excerpts from Tom Lane's message of jue jun 02 15:49:53 -0400 2011:
> Alexey Klyukin writes:
> > - Try to actually allocate the shared memory in a way postmaster does this
> > nowadays, if the process fails - analyze the error code to check whether
> > the
> > failure is due to the shmmax or
On Jun 2, 2011, at 10:49 PM, Tom Lane wrote:
> Alexey Klyukin writes:
>> We've recently come across the task of estimating the size of shared memory
>> required for PostgreSQL to start.
>
>> ...
>
>> - Try to actually allocate the shared memory in a way postmaster does this
>> nowadays, if th
On 02.06.2011 21:58, Alexey Klyukin wrote:
Hello,
We've recently come across the task of estimating the size of shared memory
required for PostgreSQL to start. This comes from the problem of validating
postgresql.conf files
(http://archives.postgresql.org/pgsql-hackers/2011-03/msg01831.php), i.e
Excerpts from Tom Lane's message of jue jun 02 15:49:53 -0400 2011:
> The results of such a test wouldn't be worth the electrons they're
> written on anyway: you're ignoring the likelihood that two instances of
> shared memory would overrun the kernel's SHMALL limit, when a single
> instance would
Alexey Klyukin writes:
> We've recently come across the task of estimating the size of shared memory
> required for PostgreSQL to start.
> ...
> - Try to actually allocate the shared memory in a way postmaster does this
> nowadays, if the process fails - analyze the error code to check whether
Hello,
We've recently come across the task of estimating the size of shared memory
required for PostgreSQL to start. This comes from the problem of validating
postgresql.conf files
(http://archives.postgresql.org/pgsql-hackers/2011-03/msg01831.php), i.e.
checking that the server will be able to st
