From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Jeff Davis <jdavis(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Add contrib/pg_walinspect. |
Date: | 2022-04-26 05:13:31 |
Message-ID: | Ymd/e5eeZMNAkrXo@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Hi Jeff,
On Fri, Apr 08, 2022 at 07:27:44AM +0000, Jeff Davis wrote:
> Add contrib/pg_walinspect.
>
> Provides similar functionality to pg_waldump, but from a SQL interface
> rather than a separate utility.
The tests of pg_walinspect look unstable:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=topminnow&dt=2022-04-25%2001%3A48%3A47
SELECT COUNT(*) >= 0 AS ok FROM
pg_get_wal_records_info_till_end_of_wal(:'wal_lsn1');
- ok
-----
- t
-(1 row)
-
+ERROR: could not read WAL at 0/1903E40
This points out at ReadNextXLogRecord(), though I would not blame this
test suite as you create a physical replication slot beforehand.
Could this be an issue related to the addition of the circular WAL
decoding buffer, aka 3f1ce97?
I am adding an open item about that.
Thanks,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-26 05:25:14 | Re: pgsql: Add contrib/pg_walinspect. |
Previous Message | Michael Paquier | 2022-04-26 04:41:23 | pgsql: Add some isolation tests for CLUSTER |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-04-26 05:17:11 | Re: CLUSTER on partitioned index |
Previous Message | Julien Rouhaud | 2022-04-26 04:54:35 | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |