Jeff Janes writes:
> On Mon, May 13, 2013 at 2:00 PM, Alvaro Herrera
> wrote:
>> Jeff Janes escribió:
>>> I think "reassign owned" should detect that it is being invoked on the
>>> internal user (as it does now) but then instead of refusing to run, it
>>> should DWIM.
>> Hm, so what would you ha
On Mon, May 13, 2013 at 2:00 PM, Alvaro Herrera wrote:
> Jeff Janes escribió:
>
> > I think "reassign owned" should detect that it is being invoked on the
> > internal user (as it does now) but then instead of refusing to run, it
> > should DWIM. I suppose that was not implemented because it is d
Jeff Janes escribió:
> I think "reassign owned" should detect that it is being invoked on the
> internal user (as it does now) but then instead of refusing to run, it
> should DWIM. I suppose that was not implemented because it is difficult to
> do so (but of course that is all the more reason no
On Mon, May 13, 2013 at 9:13 AM, Vincent Veyron wrote:
> Le mercredi 08 mai 2013 à 14:11 -0700, Jeff Janes a écrit :
> > Let's say you have a database which is owned (as well as all the
> > contents within it) by the postgres internal user.
> >
> >
> > Having created or inherited a mess, how do y
Le mercredi 08 mai 2013 à 14:11 -0700, Jeff Janes a écrit :
> Let's say you have a database which is owned (as well as all the
> contents within it) by the postgres internal user.
>
>
> Having created or inherited a mess, how do you fix it?
>
with sed on Linux/Unix, you could do this :
pg_du
