Re: Two-phase update of restart_lsn in LogicalConfirmReceivedLocation - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Two-phase update of restart_lsn in LogicalConfirmReceivedLocation
Date
Msg-id CA+TgmoZ-SW3AEMFYjSZRdLJhB3kH2=h0sG1AHdjJRxtGEcREgA@mail.gmail.com
Whole thread Raw
In response to Re: Two-phase update of restart_lsn in LogicalConfirmReceivedLocation  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Two-phase update of restart_lsn in LogicalConfirmReceivedLocation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Mar 1, 2018 at 2:03 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> So I can't say it's definitely impossible. It seems astonishingly unlikely,
> but that's not always good enough.

Race conditions tend to happen a lot more often than one might think.
If there's a theoretical opportunity for this to go wrong, it would
probably be a good idea to fix it.  Not that I'm volunteering.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: unused includes in test_decoding
Next
From: Tom Lane
Date:
Subject: Re: faster testing with symlink installs