Re: POC and rebased patch for CSN based snapshots - Mailing list pgsql-hackers

From movead.li@highgo.ca
Subject Re: POC and rebased patch for CSN based snapshots
Date
Msg-id 2020061912364160415939@highgo.ca
Whole thread Raw
In response to POC and rebased patch for CSN based snapshots  (Movead Li <movead.li@highgo.ca>)
Responses Re: POC and rebased patch for CSN based snapshots  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers

>You mean that the last generated CSN needs to be WAL-logged because any smaller
>CSN than the last one should not be reused after crash recovery. Right?
Yes that's it. 

>If right, that WAL-logging seems not necessary because CSN mechanism assumes
>CSN is increased monotonically. IOW, even without that WAL-logging, CSN afer
>crash recovery must be larger than that before. No?

CSN collected based on time of  system in this patch, but time is not reliable all the
time. And it designed for Global CSN(for sharding) where it may rely on CSN from
other node , which generated from other machine. 

So monotonically is not reliable and it need to keep it's largest CSN in wal in case
of crash.


Regards,
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Missing HashAgg EXPLAIN ANALYZE details for parallel plans
Next
From: vignesh C
Date:
Subject: Re: Cleanup - Removal of unused function parameter from CopyReadBinaryAttribute