RE: Commit Timestamp and LSN Inversion issue - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Commit Timestamp and LSN Inversion issue
Date
Msg-id TYAPR01MB5692A5C71E2355A78E36E5D2F55A2@TYAPR01MB5692.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: Commit Timestamp and LSN Inversion issue  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-hackers
Dear Andres,

> I don't think the suggested workload is useful here.
> pg_logical_emit_message(transactional = false)
> does insert the WAL without the commit, i.e., xlcommitrecis always NULL.
> This means backends won't go through added codes in
> ReserveXLogInsertLocation().

Just in case I want to clarify what I used.
My head was bfeeb06 and I applied [1] atop it.

[1]:
https://www.postgresql.org/message-id/OS0PR01MB57162A227EC357482FEB4470945D2%40OS0PR01MB5716.jpnprd01.prod.outlook.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED




pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Virtual generated columns
Next
From: Ashutosh Bapat
Date:
Subject: Re: logical replication: restart_lsn can go backwards (and more), seems broken since 9.4