Re: BUG #16703: pg-dump fails to process recursive view definition - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16703: pg-dump fails to process recursive view definition
Date
Msg-id 1571034.1604675132@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16703: pg-dump fails to process recursive view definition  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16703: pg-dump fails to process recursive view definition
List pgsql-bugs
Andrew Bille <andrewbille@gmail.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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16705: Triggers deferred during commit callback are not executed
Next
From: Ross Biro
Date:
Subject: Re: BUG #16705: Triggers deferred during commit callback are not executed