On 2014-08-14 12:21:38 -0400, Robert Haas wrote: > On Sat, Aug 9, 2014 at 12:54 PM, Andres Freund <and...@2ndquadrant.com> wrote: > > I don't think we really need to embed it at that level. And it doesn't > > have to be always on - only clients that ask for it need to get the > > answer. Something like COMMIT WITH (report_commit_lsn ON); or similar > > might do the trick? > > And what does that actually do? Send back a result-set, or a new > protocol message?
What I was thinking of was to return "COMMIT X/X" instead of "COMMIT". Since that's only sent when COMMIT WITH (report_commit_lsn ON) was set it won't break clients/libraries that don't need it. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
