shmget error text reports funny max_connections numbers

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: shmget error text reports funny max_connections numbers
Date: 2010-10-13 18:39:36
Message-ID: 1286995176.4671.3.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Since MaxBackends is actually max_connections + autovacuum_max_workers +
1, when you get an error message from shmget() it will tell you

"reduce ... its max_connections parameter (currently 104)"

when you actually set

max_connections = 100

This looks a bit silly.

Should we just make the error messages report MaxBackends -
autovacuum_max_workers - 1, or is it worthwhile calling out
autovacuum_max_workers separately?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Hunsaker 2010-10-13 19:09:22 Re: Slow count(*) again...
Previous Message Bruce Momjian 2010-10-13 18:32:22 Why do we have a database specification in .pgpass?