Re: Remaining Streaming Replication Open Items

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remaining Streaming Replication Open Items
Date: 2010-04-09 08:18:35
Message-ID: p2x3f0b79eb1004090118x93607299v158099e029b85871@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 8, 2010 at 11:00 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I think you could shut it down at the first point at which it is
> holding no locks, rather than letting it continue recovering and
> potentially retake some new locks.  That would be more consistent with
> the general idea of what a smart shutdown is supposed to be about.  I
> think the real question is whether it's worth the code complexity.

I don't think it's worth. So I agree to just remove the TODO item:
"Redefine smart shutdown in standby mode to exist as soon as all
read-only connections are gone."
http://wiki.postgresql.org/wiki/Todo#Standby_server_mode

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Łukasz Dejneka 2010-04-09 08:58:33 How to modify default Type (TSQuery) behaviour?
Previous Message Dimitri Fontaine 2010-04-09 08:10:40 Re: extended operator classes vs. type interfaces