Search Postgresql Archives

Re: Logical Replication Sync Validation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On Apr 18, 2023, at 03:45, Robert Sjöblom <robert.sjoblom@xxxxxxxxxx> wrote:
> I'm aware of that. But you can, however, do something like:
> 
> SELECT * FROM FOO WHERE CTID = (SELECT MAX(CTID) FROM FOO);
> 
> on both sides. The idea being that if I change FOO, the CTID of the changed row will not be the same on both sides, but the CTID will point to the changed row on both sides. Or am I not understanding it correctly?

CTIDs are not monotonically increasing; they're locator in the file that holds the table data.  There's no reason to believe that a record on the subscriber will happen to land in any particular position.





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux