| 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 01:47:53 |
| Message-ID: | 295868.1651024073@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:
> 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.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| debug.patch | text/x-diff | 1.4 KB |
| fail.log | text/plain | 3.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2022-04-27 01:54:34 | Re: pgsql: Add contrib/pg_walinspect. |
| Previous Message | Thomas Munro | 2022-04-27 01:10:50 | Re: pgsql: Add contrib/pg_walinspect. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2022-04-27 01:54:34 | Re: pgsql: Add contrib/pg_walinspect. |
| Previous Message | Kyotaro Horiguchi | 2022-04-27 01:43:53 | Re: Possible corruption by CreateRestartPoint at promotion |