Re: [GENERAL] dangling permission on tables after drop user.

2004-10-06 Thread Andrew Sullivan
On Thu, Sep 30, 2004 at 10:03:29AM -0400, Alvaro Herrera wrote: > > I'm afraid you'll have to ALTER TABLE (or whatever) for each of these ... > I don't think there is a command that would help you do that > automatically. You can cheat by looking at system catalogs for the > acl column (e.g. pg_

Re: [GENERAL] dangling permission on tables after drop user.

2004-09-30 Thread Alvaro Herrera
On Thu, Sep 30, 2004 at 09:32:30AM -0400, Vivek Khera wrote: > > On Sep 29, 2004, at 5:35 PM, Alvaro Herrera wrote: > > >>>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 >

Re: [GENERAL] dangling permission on tables after drop user.

2004-09-30 Thread Vivek Khera
On Sep 29, 2004, at 5:35 PM, Alvaro Herrera wrote: 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; Ok. I did that. So now how do I ge

Re: [GENERAL] dangling permission on tables after drop user.

2004-09-29 Thread Tom Lane
Vivek Khera <[EMAIL PROTECTED]> writes: > On Sep 29, 2004, at 4:55 PM, Richard Huxton wrote: >> Am I missing something Vivek, or should the gross hack be "creating a >> user with id=102" ? > And how exactly does one accomplish this? CREATE USER. regards, tom lane --

Re: [GENERAL] dangling permission on tables after drop user.

2004-09-29 Thread Alvaro Herrera
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 th

Re: [GENERAL] dangling permission on tables after drop user.

2004-09-29 Thread Vivek Khera
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

Re: [GENERAL] dangling permission on tables after drop user.

2004-09-29 Thread Richard Huxton
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

[GENERAL] dangling permission on tables after drop user.

2004-09-29 Thread Vivek Khera
I have a database which started on Pg 7.1, moved to 7.2 via pg_dump/restore, and ultimately to Pg 7.4 likewise. While it was in 7.2, I added one user and granted access to various tables. After the 7.4 migration, that user was no longer needed, so was removed via "dropuser" command line tool.