From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Remaining 9.5 open items |
Date: | 2015-12-04 19:18:10 |
Message-ID: | 14216.1449256690@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:
>> If you're speaking of section 20.4, that text is all my fault ... but
>> I'm not clear on what you think needs to be added? The first DROP OWNED
>> BY will take care of any privileges on shared objects, so I didn't really
>> think we need to burden the recipe with that detail.
> Specifically this:
> ...
> Isn't quite right, as databases which are owned by the role you're
> trying to get rid of won't be dropped.
Ah, good point. I'll add something about that. I'm not sure that we
should talk about shared objects in general, since as you say databases
are the only instance. It would feel like handwaving I think. The point
of that section IMO is to be as concrete as we can be about how to drop
a role.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-12-04 20:15:42 | Re: Foreign join pushdown vs EvalPlanQual |
Previous Message | Stephen Frost | 2015-12-04 18:52:16 | Re: Remaining 9.5 open items |