| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: Recent pg_rewind test failures in buildfarm |
| Date: | 2025-04-15 05:50:32 |
| Message-ID: | Z/3zqBCAy6zgd+t8@ip-10-97-1-34.eu-west-3.compute.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Tue, Apr 15, 2025 at 08:00:00AM +0300, Alexander Lakhin wrote:
> Hello Tom,
>
> 15.04.2025 05:58, Tom Lane wrote:
> > In the last day or so, both skink and mamba have hit this
> > in the pg_rewind test suite [1][2]:
> >
> > #3 0x01f03f7c in ExceptionalCondition (conditionName=conditionName(at)entry=0x2119c4c "pending_since == 0", fileName=fileName(at)entry=0x2119454 "pgstat.c", lineNumber=lineNumber(at)entry=734) at assert.c:66
> > ...
> >
> > That assert appears to be several years old, and the
> > 008_min_recovery_point.pl test script that's triggering it hasn't
> > changed very recently either, so I'm baffled where to start digging.
> > It has the odor of a timing problem, so maybe we just started hitting
> > this by chance. Still ... anybody have an idea?
Sorry, can't look at the details right now but it might be linked to
039549d70f6 which is recent enough and in this area. Will give it a look once
I've time.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-04-15 06:02:15 | Re: Recent pg_rewind test failures in buildfarm |
| Previous Message | Pavel Stehule | 2025-04-15 05:44:46 | Re: pg_dump --if-exists --clean when drop index that is partition of a partitioned index |