Re: Reporting the commit LSN at commit time - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Reporting the commit LSN at commit time
Date
Msg-id CAM-w4HOJosvsa8cYR2BDcz-W3p9Z8VmQLtuVuWKYa8H5xOow2Q@mail.gmail.com
Whole thread Raw
In response to Re: Reporting the commit LSN at commit time  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Tue, Aug 19, 2014 at 1:21 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> There's plenty of agreement on "not a GUC" - but what about alternatives?

It could be a new protocol message. Currently there are no transaction
oriented protocol messages (other than the "transaction status" in
ReadyForQuery). But would it not make sense to have TransactionBegin,
TransactionCommit, and TransactionAbort in the protocol? Would that
make it easier for the client-side failover to keep track of what
transactions are pending or committed and need to be verified after a
failover?


-- 
greg



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: PoC: Partial sort
Next
From: Andres Freund
Date:
Subject: Re: Reporting the commit LSN at commit time