Re: Reporting the commit LSN at commit time
От | Craig Ringer |
---|---|
Тема | Re: Reporting the commit LSN at commit time |
Дата | |
Msg-id | 53F3556E.6090908@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: Reporting the commit LSN at commit time (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: Reporting the commit LSN at commit time
|
Список | pgsql-hackers |
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. 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
В списке pgsql-hackers по дате отправления: