Re: Sync Rep and shutdown Re: Sync Rep v19

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, 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 16:37:44
Message-ID: AANLkTikELmNdf0k3eJVUzEKHEScS5haKuGdhgbiYCNFZ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 18, 2011 at 11:58 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 18.03.2011 17:38, Jeff Davis wrote:
>>
>> On Fri, 2011-03-18 at 10:27 -0400, Robert Haas wrote:
>>>
>>> ERRCODE_(WARNING_?)REPLICATION_WAIT_CANCELLED
>>>
>>> ...which might have something to recommend it.
>>
>> Works for me.
>
> Yes, sounds reasonable. Without "WARNING_", please.

The reason I included WARNING is because warnings have their own
section in errcodes.txt, and each errcode is marked E for error or W
for warning. Since we CAN'T actually error out here, I thought it
might be more appropriate to make this a warning; and all of the
existing such codes contain WARNING.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-18 16:46:03 Re: pgindent (was Re: Header comments in the recently added files)
Previous Message Robert Haas 2011-03-18 16:33:26 Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.