Re: Role membership and DROP

On Wed, 2019-11-13 at 17:17 -0500, Tom Lane wrote: > Laurenz Albe writes: > > I realized only today that if role A is a member of role B, > > A can ALTER and DROP objects owned by B. > > I don't have a problem with that, but the documentation seems to > > suggest otherwise. For example, for DROP

Re: Role membership and DROP

Laurenz Albe writes: > On Wed, 2019-11-13 at 17:17 -0500, Tom Lane wrote: >> It might be worth clarifying this point in section 5.7, >> https://www.postgresql.org/docs/devel/ddl-priv.html >> but let's not duplicate that in every ref/ page. > I have attached a proposed patch. The right to

Re: no mention of GRANT USAGE in postgres_fdw docs

PG Doc comments form writes: > The documentation page for postgres_fdw > gives a nice > step by step on what's needed to configure a FOREIGN SERVER. However, one > crucial step is missed, and that is that you need to issue GRANT USAGE ON

Add for ALTER TEXT SEARCH CONFIGURATION

If you alter one of the built-in text search configurations, the modifications to it will not get dumped by pg_dump, and thus won't get propagated by pg_upgrade leading to silent behavior changes in the new cluster (as well in any other type of restoration from pg_dump output) I would say it is ba

Re: no mention of GRANT USAGE in postgres_fdw docs

On Fri, Nov 15, 2019 at 12:05 PM Tom Lane wrote: > PG Doc comments form writes: > > The documentation page for postgres_fdw > > gives a nice > > step by step on what's needed to configure a FOREIGN SERVER. However, > one > > crucial st

Re: no mention of GRANT USAGE in postgres_fdw docs

"David G. Johnston" writes: > On Fri, Nov 15, 2019 at 12:05 PM Tom Lane wrote: >> I'm not clear why we should duplicate that information here, especially >> when we're not duplicating any of the other essential information about >> how to use IMPORT FOREIGN SCHEMA. Nor does this summary mention