On 2014-08-12 13:11:55 -0400, Tom Lane wrote:
> Andres Freund <and...@2ndquadrant.com> writes:
> > On 2014-08-12 11:56:41 -0400, Robert Haas wrote:
> >> Yes. Do you have a back-patchable solution for that?
>
> > The easiest thing I can think of is sprinkling a few
> > SetConfigOption('synchronous_commit', 'off',
> > PGC_INTERNAL, PGC_S_OVERRIDE,
> > GUC_ACTION_LOCAL, true, ERROR);
>
> This still seems to me to be applying a band-aid that covers over some
> symptoms; it's not dealing with the root cause that we've overloaded
> the signal handling mechanism too much. What reason is there to think
> that there are no other symptoms of that?
I'm not arguing against fixing that. I think we need to do both,
although I am wary of fixing the signal handling in the back
branches. Fixing the signal handling won't get rid of the problem that
one e.g. might not be able to log in anymore if all synchronous standbys
are down and login caused hot pruning.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
