Re: testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges? - Mailing list pgsql-testers

From Josh Berkus
Subject Re: testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges?
Date
Msg-id 4BE9C8D6.9040603@agliodbs.com
Whole thread Raw
In response to testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges?  (Lou Picciano <loupicciano@comcast.net>)
List pgsql-testers
Lou,

> *[Comments]:* Is this consistent behavior?  Is it necessary to
> explicitly grant privileges to each object in a database?

This is correct, and how it's been for PostgreSQL since at least 7.2.

> We are aware of the new ALTER DEFAULT PRIVILEGES command, but, per docs,
> it only affects  tables (including views), sequences, and functions,
> correct?
> IE, it cannot affect database privileges.

That's correct.  However, it's only necessary to set database priveleges
once.

--
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com

pgsql-testers by date:

Previous
From: Lou Picciano
Date:
Subject: testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges?
Next
From: Josh Berkus
Date:
Subject: Re: testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges?