Re: dangling permission on tables after drop user. - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: dangling permission on tables after drop user.
Date
Msg-id 20040929213558.GA6199@dcc.uchile.cl
Whole thread Raw
In response to Re: dangling permission on tables after drop user.  (Vivek Khera <khera@kcilink.com>)
Responses Re: dangling permission on tables after drop user.  (Vivek Khera <khera@kcilink.com>)
List pgsql-general
On Wed, Sep 29, 2004 at 05:07:38PM -0400, Vivek Khera wrote:
>
> On Sep 29, 2004, at 4:55 PM, Richard Huxton wrote:
>
> >Vivek Khera wrote:
> >>there is no user with ID 102 in the pg_user view.  pg_restore
> >>complains about the missing user "102".  And no, the user was not
> >>"102" it was the name of a (former) employee.
> >
> >>The gross hack is to pg_restore to an ascii file and delete those
> >>GRANT lines, but the compressed dump is over 2Gb for this database.
> >
> >Am I missing something Vivek, or should the gross hack be "creating a
> >user with id=102" ?
>
> And how exactly does one accomplish this?  pg_users is a view so you
> can't insert into it.

CREATE USER ... WITH SYSID 102;

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
Dios hizo a Adán, pero fue Eva quien lo hizo hombre.


pgsql-general by date:

Previous
From: Vivek Khera
Date:
Subject: Re: dangling permission on tables after drop user.
Next
From: Thomas F.O'Connell
Date:
Subject: Index Analysis: Filters