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

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Lou Picciano <loupicciano(at)comcast(dot)net>
Cc: pgsql-testers(at)postgresql(dot)org
Subject: Re: testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges?
Date: 2010-05-11 21:15:02
Message-ID: 4BE9C8D6.9040603@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-testers by date

  From Date Subject
Next Message Josh Berkus 2010-05-11 23:04:27 Re: testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges?
Previous Message Lou Picciano 2010-05-11 20:41:00 testing simple SELECT commands on newly-created databases. Apparently blocked by (lack of) privileges?