Re: Reset ACL to default for pg 8.0

From: "Juan C(dot) Aragon" <juan(at)keisercomputers(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Bruce Momjian'" <bruce(at)momjian(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Reset ACL to default for pg 8.0
Date: 2010-04-16 14:27:51
Message-ID: 001d01cadd70$ff1ff300$fd5fd900$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom:

Is there a way to set it back to built-in-default permissions?

Juan C. Aragon

-----Original Message-----
From: pgsql-bugs-owner(at)postgresql(dot)org
[mailto:pgsql-bugs-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Friday, April 16, 2010 12:33 AM
To: Bruce Momjian
Cc: Juan C. Aragon; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] Reset ACL to default for pg 8.0

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Community, do we want to make a permission reset cause the column to
> become null?

That's not a permission reset.

>> I just need to know if the brackets are normal when all the privileges
are
>> remove. Or how to reset the privileges (ACL) to default (null).

> They are the same.

Nope, they're not. NULL implies the built-in-default permissions, which
are quite different from the empty set.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-04-16 21:03:37 Re: build error: strlcat/strlcpy used from heimdal libroken.so
Previous Message Tom Lane 2010-04-16 13:51:54 Re: BUG #5427: Using CASE in plpgsql causes 'ERROR: cache lookup failed'