| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Bille <andrewbille(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16703: pg-dump fails to process recursive view definition |
| Date: | 2020-11-06 15:05:32 |
| Message-ID: | 1571034.1604675132@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andrew Bille <andrewbille(at)gmail(dot)com> writes:
> pg_dump is also fails to process the view created by the following script
> (excerpt from privileges.sql):
> CREATE USER user1;
> CREATE TABLE test (col1 varchar(10), col2 boolean);
> SET SESSION AUTHORIZATION user1;
> CREATE VIEW testv AS SELECT * FROM test;
Hm, yeah, so more to do here. (Sure glad we found these issues before
next week's releases, not after.)
I propose that what we'd better do is
(1) Make pg_dump use LOCK TABLE ONLY, not LOCK TABLE.
(2) Make LOCK TABLE ONLY on a view not recurse to the view's dependencies.
It's quite unclear to me why it didn't work that way all along.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross Biro | 2020-11-06 15:14:54 | Re: BUG #16705: Triggers deferred during commit callback are not executed |
| Previous Message | Tom Lane | 2020-11-06 14:49:58 | Re: BUG #16705: Triggers deferred during commit callback are not executed |