| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:36:05 |
| Message-ID: | YmeExX6ACB/Et9Ww@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, Apr 26, 2022 at 01:25:14AM -0400, Tom Lane wrote:
> 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.
I have managed to miss your message. Let's continue the discussion
there, then.
> 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.
Nice. I have not been able to do so, but based on the lack of
reports from the buildfarm, that's not surprising.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2022-04-27 00:06:30 | Re: pgsql: Add contrib/pg_walinspect. |
| Previous Message | Michael Paquier | 2022-04-26 05:25:42 | pgsql: Fix typo in pg_walinspect.c |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | osumi.takamichi@fujitsu.com | 2022-04-26 06:02:46 | RE: Skipping schema changes in publication |
| Previous Message | Alvaro Herrera | 2022-04-26 05:28:15 | Re: CLUSTER on partitioned index |