Re: Estimating total amount of shared memory required by postmaster

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexey Klyukin <alexk(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Estimating total amount of shared memory required by postmaster
Date: 2011-06-03 04:15:49
Message-ID: 1307074462-sup-635@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 be fine.

Well, overrunning SHMALL sets a different errno than overrunning SHMMAX,
so at least it's possible to notice the problem.

> Given that you can't do it in the context of a live installation, just
> trying to start the postmaster and seeing if it works (same as initdb
> does) seems as good as anything else.

That's precisely what this is trying to avoid.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-06-03 04:27:35 Re: Domains versus polymorphic functions, redux
Previous Message Jim Nasby 2011-06-03 03:58:33 Re: storing TZ along timestamps