Re: pg_get_expr locking

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_get_expr locking
Date: 2024-02-08 11:18:17
Message-ID: ecd0ea46-ba4e-4611-8fc0-fbe118d7c27d@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07.02.24 16:26, Tom Lane wrote:
>> What workaround should we use if there are conflicts created by
>> concurrent regression tests? Just move the tests around a bit until the
>> issue goes away?
>
> Why would a test be applying pg_get_expr to a table it doesn't
> control?

I think the situation is that one test (domain) runs pg_get_expr as part
of an information_schema view, while at the same time another test
(alter_table) drops a table that the pg_get_expr is just processing.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2024-02-08 11:19:53 Re: Refactoring backend fork+exec code
Previous Message Majid Garoosi 2024-02-08 11:12:00 Re: GUC-ify walsender MAX_SEND_SIZE constant