469,333 Members | 4,354 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,333 developers. It's quick & easy.

Phantom user in db--'128'

I posted this earlier, and got no responses.
While using pg_dump and pg_restore (or attempting to restore, more
precisely), the process failed because of a missing user, user '128'. I
never created such a user, and when going to Privileges, such a user does
not exist in the list. However, while going out and checking some of the
tables, this user shows up as a user with privileges on them (however, not
on all tables). How do I get rid of this user? And how do I ensure that it
doesn't get created again? I'd like to understand what is really going on
before hacking the user table.
Thanks in advance.
Mark Taber
State of California
Department of Finance
Infrastructure & Architecture

916.323.3104 x 2945
ma********@dof.ca.gov
Nov 23 '05 #1
1 2318
"Taber, Mark" <Ma********@dof.ca.gov> writes:
While using pg_dump and pg_restore (or attempting to restore, more
precisely), the process failed because of a missing user, user '128'. I
never created such a user, and when going to Privileges, such a user does
not exist in the list. However, while going out and checking some of the
tables, this user shows up as a user with privileges on them (however, not
on all tables). How do I get rid of this user? And how do I ensure that it
doesn't get created again? I'd like to understand what is really going on


You had a user with usesysid 128, whom you dropped, but he still had
privileges on some tables --- DROP USER is not good about detecting
dangling references.

I'd suggest recreating the user (CREATE USER foo WITH SYSID 128) and
then being careful to REVOKE all his privileges before you drop him
again. Or you can just manually edit the dump file to remove the
attempts to GRANT him privileges.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Andrew | last post: by
reply views Thread by Shaphe | last post: by
3 posts views Thread by memememe | last post: by
reply views Thread by Rod Billett | last post: by
9 posts views Thread by Dave | last post: by
9 posts views Thread by TB | last post: by
12 posts views Thread by DanG | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
1 post views Thread by Marylou17 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.