Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types.
Date: 2015-08-10 21:48:44
Message-ID: 15657.1439243324@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

I wrote:
> But now that you mention it, isn't that completely broken? What pg_dump
> actually prints given this made-up data is

> REVOKE ALL ON TYPE myshell FROM PUBLIC;
> REVOKE ALL ON TYPE myshell FROM postgres;
> GRANT ALL ON TYPE myshell TO PUBLIC;

> which seems like a completely insane interpretation. There is no way
> that dumping a type from a pre-typacl database and restoring it into
> a newer one should end up with the type's owner having no privileges
> on it. I'm astonished that we've not gotten bug reports about that.

... of course, the reason for no field reports is that the owner still
has privileges, as she inherits them from PUBLIC. Doesn't make this
any less broken though.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-08-10 23:29:04 Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types.
Previous Message Tom Lane 2015-08-10 21:35:08 pgsql: Accept alternate spellings of __sparcv7 and __sparcv8.

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-08-10 21:48:51 Re: linux sparc compile issue
Previous Message Tom Lane 2015-08-10 21:36:57 Re: linux sparc compile issue