Sync Rep and shutdown Re: Sync Rep v19

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Sync Rep and shutdown Re: Sync Rep v19
Date: 2011-03-09 07:38:00
Message-ID: AANLkTimkFfXcA8=W4+Jt4sAgXPB1DApiUgbibw1HRZcj@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 9, 2011 at 2:14 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> On Tue, Mar 8, 2011 at 11:58 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>
>> The fast shutdown handling seems fine, but why not just handle smart
>> shutdown the same way?
>
> currently, smart shutdown means no new connections, wait until
> existing ones close normally. for consistency, it should behave the
> same for sync rep.

Agreed. I think that user who wants to request smart shutdown expects all
the existing connections to basically be closed normally by the client. So it
doesn't seem to be good idea to forcibly close the connection and prevent
the COMMIT from being returned in smart shutdown case. But I'm all ears
for better suggestions.

Anyway, we got the consensus about how fast shutdown should work with
sync rep. So I created the patch. Please feel free to comment and commit
the patch first ;)

Regards,

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

Attachment Content-Type Size
fast_shutdown_syncrep_v1.patch application/octet-stream 4.6 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yeb Havinga 2011-03-09 08:14:48 Re: Sync Rep and shutdown Re: Sync Rep v19
Previous Message Jaime Casanova 2011-03-09 05:14:01 Re: Sync Rep v19