From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: type privileges and default privileges |
Date: | 2011-11-11 03:41:13 |
Message-ID: | 23982.1320982873@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> To actually get rid of acldefault, we'd have to do that not only for
>> types but for all objects with ACLs. That's a LOT of catalog bulk,
>> and like Robert I'm not seeing much benefit. It's not unreasonable
>> to want the typical case to be small and fast.
> A LOT of catalog bulk..? Am I missing something here?
What I'm missing is what actual benefit we get from spending the extra
space. (No, I don't believe that changing the defaults is something
that users commonly will or should do; it's certainly not the case to
optimize for.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2011-11-11 03:52:23 | Re: type privileges and default privileges |
Previous Message | Alvaro Herrera | 2011-11-11 03:32:33 | Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID |