From: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Steve Singer <steve(at)ssinger(dot)info> |
Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Anssi Kääriäinen <anssi(dot)kaariainen(at)thl(dot)fi>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Subject: | Re: tracking commit timestamps |
Date: | 2014-11-13 13:41:36 |
Message-ID: | 5464B510.2020601@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On 13/11/14 14:18, Simon Riggs wrote:
>
> So in summary... the components are
> * Commit LSN order is useful for applying changes - available by
> logical decoding
> * Commit timestamps and nodeid are useful for conflict resolution -
> available from this patch
>
> Both components have been designed in ways that allow multiple
> replication systems to use these facilities.
>
> So, -1 to including commit LSN in the SLRU alongside commit timestamp
> and nodeid.
>
I am of the same opinion, I added the LSN "by popular demand", but I
still personally don't see the value in having it there as it does *not*
enable us to do something that would be impossible otherwise.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Ants Aasma | 2014-11-13 14:13:04 | Re: Failback to old master |
Previous Message | Heikki Linnakangas | 2014-11-13 13:33:44 | Re: WAL format and API changes (9.5) |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-11-13 21:24:52 | Re: tracking commit timestamps |
Previous Message | Simon Riggs | 2014-11-13 13:18:22 | Re: tracking commit timestamps |