Skip site navigation (1) Skip section navigation (2)

Re: dangling permission on tables after drop user.

From: Vivek Khera <khera(at)kcilink(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: dangling permission on tables after drop user.
Date: 2004-09-29 21:07:38
Message-ID: 981B8910-125B-11D9-8D20-000A9578CFCC@kcilink.com (view raw or flat)
Thread:
Lists: 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


In response to

Responses

pgsql-general by date

Next:From: Alvaro HerreraDate: 2004-09-29 21:35:58
Subject: Re: dangling permission on tables after drop user.
Previous:From: Richard HuxtonDate: 2004-09-29 20:55:14
Subject: Re: dangling permission on tables after drop user.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group