From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: How should the waiting backends behave in sync rep? |
Date: | 2011-03-16 08:44:44 |
Message-ID: | 1300265084.20494.7538.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2011-03-16 at 16:36 +0900, Fujii Masao wrote:
> On Sat, Mar 12, 2011 at 3:12 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > There's a comment that looks related to this issue in syncrep.c. It reads:
> >
> > /*
> > * We don't receive SIGHUPs at this point, so resetting
> > * synchronous_standby_names has no effect on waiters.
> > */
> >
> > It's unclear to me what this actually means. Is there some reason we
> > CAN'T receive SIGHUPs at that point, or have we just chosen not to
> > (for unexplained reasons)?
>
> Not sure. Simon?
>
> It seems harmless to receive SIGHUP at that point.
You pointed out this out to me, so if you want I can explain back to you
again ;-) Signals are blocked over that section of code.
We could write a scary bit of code to get around that, but it smells
badly of kludge.
What do you think we should do?
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-03-16 08:51:14 | Re: Sync Rep and shutdown Re: Sync Rep v19 |
Previous Message | Simon Riggs | 2011-03-16 08:41:12 | Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |