Re: waiting for reload in tests

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: waiting for reload in tests
Date: 2022-05-10 01:42:20
Message-ID: 4017423.1652146940@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-05-10 01:51:46 Re: [PoC] Improve dead tuple storage for lazy vacuum
Previous Message Michael Paquier 2022-05-10 01:37:46 Re: waiting for reload in tests