Re: Sync Rep and shutdown Re: Sync Rep v19 - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Sync Rep and shutdown Re: Sync Rep v19
Date
Msg-id 1300457873.3474.97.camel@jdavis
Whole thread Raw
In response to Re: Sync Rep and shutdown Re: Sync Rep v19  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Sync Rep and shutdown Re: Sync Rep v19
List pgsql-hackers
On Fri, 2011-03-18 at 08:27 -0400, Robert Haas wrote:
> On Thu, Mar 17, 2011 at 6:00 PM, Jeff Davis <pgsql@j-davis.com> wrote:
> > On Wed, 2011-03-16 at 13:35 -0400, Robert Haas wrote:
> >> 2. If a query cancel interrupt is received (pg_cancel_backend or ^C),
> >> then cancel the sync rep wait and issue a warning before acknowledging
> >> the commit.
> >
> > When I saw this commit, I noticed that the WARNING doesn't have an
> > errcode(). It seems like it should -- this is the kind of thing that the
> > client is likely to care about, and may want to handle specially.
> 
> Should I invent ERRCODE_WARNING_TRANSACTION_NOT_REPLICATED?

I think it's reasonable to invent a new code here. Perhaps use the word
"synchronous" rather than "replicated", though?

Regards,Jeff Davis




pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: FK constraints "NOT VALID" by default?
Next
From: Simon Riggs
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.