On 08/19/2014 06:21 PM, Andres Freund wrote: > What's the problem with the COMMIT WITH (report_lsn on) I've proposed? > Reporting the LSN in the command tag? Anything doing transparent > failover needs to be aware of transaction boundaries anyway.
Advertising
Tom's objection to a GUC applies there too - a client app can send that when the underlying driver doesn't expect to get the results. I'm not completely convinced that's a problem - oh dear, the app breaks. The answer to so many other things in Pg is "well, don't do that then" that I don't see this as overly different. However, granting that it is a problem, the same objection to a GUC applies to this too. -- Craig Ringer 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
