Skip site navigation (1) Skip section navigation (2)

Re: Sync Rep and shutdown Re: Sync Rep v19

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sync Rep and shutdown Re: Sync Rep v19
Date: 2011-03-18 18:55:14
Message-ID: 1300474501-sup-980@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Excerpts from Robert Haas's message of vie mar 18 14:25:16 -0300 2011:
> On Fri, Mar 18, 2011 at 1:15 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> > SyncRepUpdateSyncStandbysDefined() is added into walwriter, which means
> > waiters won't be released if we do a sighup during a fast shutdown,
> > since the walwriter gets killed as soon as that starts. I'm thinking
> > bgwriter should handle that now.
> 
> Hmm.  I was thinking that doing it in WAL writer would make it more
> responsive, but since this is a fairly unlikely scenario, it's
> probably not worth complicating the shutdown sequence to do it the way
> I did.  I'll move it to bgwriter.

Can't they both do it?

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Markus WannerDate: 2011-03-18 19:17:56
Subject: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Previous:From: Dan PortsDate: 2011-03-18 18:18:32
Subject: Re: SSI bug?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group