Re: tests against running server occasionally fail, postgres_fdw & tenk1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Fujii Masao <fujii(at)postgresql(dot)org>
Subject: Re: tests against running server occasionally fail, postgres_fdw & tenk1
Date: 2023-02-27 17:42:00
Message-ID: 389248.1677519720@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Hah - I thought of a solution. We can avoid this race condition if
> we make the remote session itself inspect pg_stat_activity and
> return its displayed application_name. Just need a foreign table
> that maps onto pg_stat_activity.

I went ahead and coded it that way, and it doesn't look too awful.
Any objections?

regards, tom lane

Attachment Content-Type Size
remove-instability-in-postgres_fdw-tests-2.patch text/x-diff 11.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-02-27 17:50:15 Re: pg_dump versus hash partitioning
Previous Message John Naylor 2023-02-27 17:07:23 Re: [PoC] Improve dead tuple storage for lazy vacuum