| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New WAL record to detect the checkpoint redo location |
| Date: | 2023-10-19 05:53:12 |
| Message-ID: | ZTDESPN-FhH697Ls@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 18, 2023 at 10:24:50AM -0400, Robert Haas wrote:
> I added a variant of this test case. Here's v10.
+-- Verify that an XLOG_CHECKPOINT_REDO record begins at precisely the redo LSN
+-- of the checkpoint we just performed.
+SELECT redo_lsn FROM pg_control_checkpoint() \gset
+SELECT start_lsn = :'redo_lsn'::pg_lsn AS same_lsn, resource_manager,
+ record_type FROM pg_get_wal_record_info(:'redo_lsn');
+ same_lsn | resource_manager | record_type
+----------+------------------+-----------------
+ t | XLOG | CHECKPOINT_REDO
+(1 row)
Seems fine to me. Thanks for considering the idea.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeevan Chalke | 2023-10-19 06:06:37 | Re: More new SQL/JSON item methods |
| Previous Message | Michael Paquier | 2023-10-19 05:26:26 | Re: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written} |