Re: waiting for reload in tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: waiting for reload in tests
Date
Msg-id 4017423.1652146940@sss.pgh.pa.us
Whole thread Raw
In response to Re: waiting for reload in tests  (Michael Paquier <michael@paquier.xyz>)
Responses Re: waiting for reload in tests
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Mon, May 09, 2022 at 09:29:32PM -0400, Tom Lane wrote:
>> Less brute force: wait for "SHOW variable-you-changed" to report the
>> value you expect.

> This method may still be unreliable in some processes like a logirep
> launcher/receiver or just autovacuum, no?

Yeah, if your test case requires knowing that some background process
has gotten the word, it's a *lot* harder.  I think we'd have to add a
last-config-update-time column in pg_stat_activity or something like that.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: waiting for reload in tests
Next
From: Masahiko Sawada
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum