Re: tracking commit timestamps
От | Robert Haas |
---|---|
Тема | Re: tracking commit timestamps |
Дата | |
Msg-id | CA+TgmoYiiivA4kZoXAszKz4QLtSBDyBkoWCRvaAJY0JS94apKw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: tracking commit timestamps (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: tracking commit timestamps
|
Список | pgsql-hackers |
On Thu, Nov 13, 2014 at 8:18 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > Ordering transactions in LSN order is very precisly the remit of the > existing logical decoding API. Any user that wishes to see a commits > in sequence can do so using that API. BDR already does this, as do > other users of the decoding API. So Slony already has access to a > useful ordering if it wishes it. We do not need to anything *on this > patch* to enable LSNs for Slony or anyone else. I don't see any reason > to provide the same facility twice, in two different ways. Perhaps you could respond more specifically to concerns expressed upthread, like: http://www.postgresql.org/message-id/BLU436-SMTP28B68B9312CBE5D9125441DC870@phx.gbl I don't see that as a dumb argument on the face of it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: