Re: Missing import in 035_standby_logical_decoding.pl

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Missing import in 035_standby_logical_decoding.pl
Date: 2025-08-04 19:16:00
Message-ID: CAAKRu_aK8X6inYHNUng3iG5hvw5q4PA3bmLzXHgGEjH6Lc+VAg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 4, 2025 at 3:49 AM Bertrand Drouvot
<bertranddrouvot(dot)pg(at)gmail(dot)com> wrote:
>
> On Fri, Aug 01, 2025 at 03:04:20PM -0400, Melanie Plageman wrote:
>
> > but it does not import usleep as other tests do (like this)
> > use Time::HiRes qw(usleep);
> >
> > I think it simply hasn't been called because postgres exits and
> > terminates the loop before it has had a chance to be called. If you
> > reorder the sleep and the loop termination condition, it fails
> > immediately because it can't find usleep.
>
> Thanks for the report! I think it's an oversight in commit 48796a98d5ae. Fixed
> in the attached.

I've committed and backported the fix.

> > On an unrelated note, I also noticed that hot_standby_feedback is not
> > turned on during the test until we are explicitly checking for
> > recovery conflicts.
>
> Yeah, it's expected.

I see. I had to change it to be on for more of the test scenarios in
my patchset which sets the VM on-access [1] (v6-0017), but I suppose
it doesn't make sense to make this change on master.

- Melanie

[1] https://www.postgresql.org/message-id/CAAKRu_bGCgUuhmy1Mzkw3yCmbGcjNQAjV%3DOmjuW6hz90PuXKWA%40mail.gmail.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2025-08-04 19:37:19 Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)
Previous Message Nathan Bossart 2025-08-04 19:12:30 Re: Improve LWLock tranche name visibility across backends