Re: pg_get_expr locking - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_get_expr locking
Date
Msg-id ecd0ea46-ba4e-4611-8fc0-fbe118d7c27d@eisentraut.org
Whole thread Raw
In response to Re: pg_get_expr locking  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_get_expr locking
List 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.




pgsql-hackers by date:

Previous
From: Majid Garoosi
Date:
Subject: Re: GUC-ify walsender MAX_SEND_SIZE constant
Next
From: Heikki Linnakangas
Date:
Subject: Re: Refactoring backend fork+exec code