From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 01:54:34 |
Message-ID: | CA+hUKG+By4isKdbDkCaLkPq4V4ECWW=d+RhcLjQXTQ3KAJLobg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Wed, Apr 27, 2022 at 1:47 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > Hrmph... Are you sure you rebuilt the contrib module? Assuming so,
> > maybe it's failing in a different way for you and me. For me, it
> > always fails after this break is reached in xlogutil.c:
>
> > /* If asked, let's not wait for future WAL. */
> > if (!wait_for_wal)
> > break;
>
> Hmm. For me, that statement is not reached at all in successful
> (make installcheck) runs. In a failing run, it's reached with
> wait_for_wal = false, after which we get the "could not read WAL"
> failure. Usually that happens twice, as per attached.
Ok, that's the same for me. Next question: why does the patch I
posted not help? For me, the error "could not read WAL at %X/%X",
seen on the BF log, is raised by ReadNextXLogRecord() in
pg_walinspect.c. The patch removes that ereport() entirely (and
handles NULL in a couple of places).
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-27 01:55:50 | Re: pgsql: Add contrib/pg_walinspect. |
Previous Message | Tom Lane | 2022-04-27 01:47:53 | Re: pgsql: Add contrib/pg_walinspect. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-27 01:55:50 | Re: pgsql: Add contrib/pg_walinspect. |
Previous Message | Tom Lane | 2022-04-27 01:47:53 | Re: pgsql: Add contrib/pg_walinspect. |