Re: TopoSort() fix - Mailing list pgsql-hackers

From Robert Haas
Subject Re: TopoSort() fix
Date
Msg-id CA+TgmobX+8Hj9Q-yREEqZGDjeMLAvKoSPt8jEs6Tc55VjVxgsg@mail.gmail.com
Whole thread Raw
In response to Re: TopoSort() fix  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TopoSort() fix
List pgsql-hackers
On Mon, Jul 29, 2019 at 9:48 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I tried that first.  There are backstops preventing doing LOCK TABLE
> in a worker, just like for advisory locks.
>
> I believe the only accessible route to taking any sort of new lock
> in a parallel worker is catalog lookups causing AccessShareLock on
> a catalog.

Can't the worker just query a previously-untouched table, maybe by
constructing a string and then using EXECUTE to execute it?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: TopoSort() fix
Next
From: Michael Paquier
Date:
Subject: Re: TopoSort() fix