Re: TopoSort() fix
| От | Robert Haas |
|---|---|
| Тема | Re: TopoSort() fix |
| Дата | |
| Msg-id | CA+TgmobX+8Hj9Q-yREEqZGDjeMLAvKoSPt8jEs6Tc55VjVxgsg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: TopoSort() fix (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: TopoSort() fix
|
| Список | 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 по дате отправления: