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

From Vivek Khera
Subject Re: dangling permission on tables after drop user.
Date
Msg-id 981B8910-125B-11D9-8D20-000A9578CFCC@kcilink.com
Whole thread Raw
In response to Re: dangling permission on tables after drop user.  (Richard Huxton <dev@archonet.com>)
Responses Re: dangling permission on tables after drop user.
Re: dangling permission on tables after drop user.
List pgsql-general
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.


Vivek Khera, Ph.D.
+1-301-869-4449 x806


pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: dangling permission on tables after drop user.
Next
From: Alvaro Herrera
Date:
Subject: Re: dangling permission on tables after drop user.