From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Florian Pflug <fgp(at)phlo(dot)org>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: max_standby_delay considered harmful |
Date: | 2010-05-12 13:15:11 |
Message-ID: | 1273670111.308.556.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2010-05-12 at 08:52 -0400, Robert Haas wrote:
> On Wed, May 12, 2010 at 7:26 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> > On Wed, 2010-05-12 at 07:10 -0400, Robert Haas wrote:
> >
> >> I'm not sure what to make of this. Sometimes not shutting down
> >> doesn't sound like a feature to me.
> >
> > It acts exactly the same in recovery as in normal running. It is not a
> > special feature of recovery at all, bug or otherwise.
>
> Simon, that doesn't make any sense. We are talking about a backend
> getting stuck forever on an exclusive lock that is held by the startup
> process and which will never be released (for example, because the
> master has shut down and no more WAL can be obtained for replay). The
> startup process does not hold locks in normal operation.
When I test it, startup process holding a lock does not prevent shutdown
of a standby.
I'd be happy to see your test case showing a bug exists and that the
behaviour differs from normal running.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2010-05-12 14:03:31 | Re: max_standby_delay considered harmful |
Previous Message | Robert Haas | 2010-05-12 12:52:15 | Re: max_standby_delay considered harmful |