Robert Haas writes:
> On Wed, Jun 29, 2011 at 8:53 PM, David Fetter wrote:
>> How about this?
>>
>> PostgreSQL grants some types of objects some default privileges to
>> PUBLIC. Tables, columns, schemas and tablespaces grant no privileges
>> to PUBLIC by default. For other types, the default p
On 06/29/2011 09:20 PM, Robert Haas wrote:
On Wed, Jun 29, 2011 at 8:53 PM, David Fetter wrote:
How about this?
PostgreSQL grants some types of objects some default privileges to
PUBLIC. Tables, columns, schemas and tablespaces grant no privileges
to PUBLIC by default. For other types, the
On Wed, Jun 29, 2011 at 8:53 PM, David Fetter wrote:
> How about this?
>
> PostgreSQL grants some types of objects some default privileges to
> PUBLIC. Tables, columns, schemas and tablespaces grant no privileges
> to PUBLIC by default. For other types, the default privileges granted
> to PUBLIC
On Wed, Jun 29, 2011 at 08:42:58PM -0400, Robert Haas wrote:
> On Wed, Jun 29, 2011 at 4:49 PM, Alvaro Herrera
> wrote:
> > Excerpts from Robert Haas's message of mié jun 29 13:42:34 -0400 2011:
> >
> >> > How about this?
> >> >
> >> > Some types of objects deny all privileges to PUBLIC by default
On Wed, Jun 29, 2011 at 4:49 PM, Alvaro Herrera
wrote:
> Excerpts from Robert Haas's message of mié jun 29 13:42:34 -0400 2011:
>
>> > How about this?
>> >
>> > Some types of objects deny all privileges to PUBLIC by default. These
>> > are tables, columns, schemas and tablespaces. For other type
On 06/29/2011 05:16 PM, David Fetter wrote:
Hmm, I like David's suggestion better, but I agree with you that
"deny" isn't the right verb there. I have no better suggestions at
moment though.
I chose "deny" in the sense of "default deny," which is a term of art
in security engineering referri
On Wed, Jun 29, 2011 at 04:49:15PM -0400, Alvaro Herrera wrote:
> Excerpts from Robert Haas's message of mié jun 29 13:42:34 -0400 2011:
>
> > > How about this?
> > >
> > > Some types of objects deny all privileges to PUBLIC by default.
> > > These are tables, columns, schemas and tablespaces. F
Excerpts from Robert Haas's message of mié jun 29 13:42:34 -0400 2011:
> > How about this?
> >
> > Some types of objects deny all privileges to PUBLIC by default. These
> > are tables, columns, schemas and tablespaces. For other types, the
> > default privileges granted to PUBLIC are as follows:
On Wed, Jun 29, 2011 at 1:20 PM, David Fetter wrote:
> On Wed, Jun 29, 2011 at 11:50:38AM -0400, Alvaro Herrera wrote:
>> Excerpts from Andrew Dunstan's message of mié jun 29 11:21:12 -0400 2011:
>> >
>> > I was just reading the docs on default privileges, and they say this:
>> >
>> > Dependin
On Wed, Jun 29, 2011 at 11:50:38AM -0400, Alvaro Herrera wrote:
> Excerpts from Andrew Dunstan's message of mié jun 29 11:21:12 -0400 2011:
> >
> > I was just reading the docs on default privileges, and they say this:
> >
> > Depending on the type of object, the initial default privileges
> >
Excerpts from Andrew Dunstan's message of mié jun 29 11:21:12 -0400 2011:
>
> I was just reading the docs on default privileges, and they say this:
>
> Depending on the type of object, the initial default privileges
> might include granting some privileges to PUBLIC. The default is no
>
I was just reading the docs on default privileges, and they say this:
Depending on the type of object, the initial default privileges
might include granting some privileges to PUBLIC. The default is no
public access for tables, columns, schemas, and tablespaces; CONNECT
privilege and
12 matches
Mail list logo
