Re: pgsql: Add contrib/pg_walinspect.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Noah Misch <noah(at)leadboat(dot)com>, Jeff Davis <jdavis(at)postgresql(dot)org>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Add contrib/pg_walinspect.
Date: 2022-04-27 02:14:25
Message-ID: 298622.1651025665@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Ok, that's the same for me. Next question: why does the patch I
> posted not help?

I improved the instrumentation a bit, and it looks like what is
happening is that loc > read_upto, causing that code to "break"
independently of wait_for_wal. success.log is from "make installcheck"
immediately after initdb; fail.log is from "make check".

regards, tom lane

Attachment Content-Type Size
debug.patch text/x-diff 1.4 KB
success.log text/plain 5.4 KB
fail.log text/plain 7.8 KB

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-04-27 02:15:16 Re: pgsql: Add contrib/pg_walinspect.
Previous Message Thomas Munro 2022-04-27 02:10:49 Re: pgsql: Add contrib/pg_walinspect.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-04-27 02:15:16 Re: pgsql: Add contrib/pg_walinspect.
Previous Message Thomas Munro 2022-04-27 02:10:49 Re: pgsql: Add contrib/pg_walinspect.