| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Jeff Davis <jdavis(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Add contrib/pg_walinspect. |
| Date: | 2022-04-26 05:25:14 |
| Message-ID: | 171769.1650950714@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> Could this be an issue related to the addition of the circular WAL
> decoding buffer, aka 3f1ce97?
I already whined about this at [1].
I've been wondering if the issue could be traced to topminnow's unusual
hardware properties, specifically that it has MAXALIGN 8 even though
it's only a 32-bit machine per sizeof(void *). I think the only
other active buildfarm animal like that is my gaur ... but I've
failed to reproduce it on gaur. Best guess at the moment is that
it's a timing issue that topminnow manages to reproduce often.
Anyway, as I said in the other thread, I can reproduce it on
topminnow's host. Let me know if you have ideas about how to
home in on the cause.
regards, tom lane
[1] https://www.postgresql.org/message-id/111657.1650910309%40sss.pgh.pa.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-04-26 05:25:42 | pgsql: Fix typo in pg_walinspect.c |
| Previous Message | Michael Paquier | 2022-04-26 05:13:31 | Re: pgsql: Add contrib/pg_walinspect. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-04-26 05:28:15 | Re: CLUSTER on partitioned index |
| Previous Message | David Rowley | 2022-04-26 05:24:02 | Re: Making JIT more granular |