I have applied a patch to improve shared memory failure reporting,
attached. We no longer report actual parameter _values_ and suggest
that other parameters might also cause such failures.
---
Alvaro Herrera wrote:
> Excerp
Excerpts from Robert Haas's message of jue oct 14 21:36:48 -0300 2010:
> On Wed, Oct 13, 2010 at 2:39 PM, Peter Eisentraut wrote:
> > Since MaxBackends is actually max_connections + autovacuum_max_workers +
> > 1, when you get an error message from shmget() it will tell you
> >
> > "reduce ... its
On Wed, Oct 13, 2010 at 2:39 PM, Peter Eisentraut wrote:
> 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_con
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
