pg_get_expr locking - Mailing list pgsql-hackers

From Peter Eisentraut
Subject pg_get_expr locking
Date
Msg-id 31ddcc01-a71b-4e8c-9948-01d1c47293ca@eisentraut.org
Whole thread Raw
Responses Re: pg_get_expr locking
List pgsql-hackers
The function pg_get_expr(), which is used in various system views and 
information schema views, does not appear to lock the table passed as 
the second argument, and so appears to be liable to fail if there is a 
concurrent drop of the table.  There is a (probable) case of this being 
discussed at [0].  I also see various mentions of this issue in the 
commit logs, mostly related to pg_dump.

Is there a reason there is no locking?  Performance?

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?


[0]: 
https://www.postgresql.org/message-id/flat/9ec24d7b-633d-463a-84c6-7acff769c9e8@eisentraut.org



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Catalog domain not-null constraints
Next
From: David Rowley
Date:
Subject: Re: An improvement on parallel DISTINCT