On Monday 01 March 2010 @ 17:26, Tom Lane wrote: > "Ed L." <pgsql@xxxxxxxxxxxxx> writes: > > On Monday 01 March 2010 @ 17:18, Tom Lane wrote: > >> "Ed L." <pgsql@xxxxxxxxxxxxx> writes: > >>> There is one, looks like a typo got in. How do I fix it? > >> > >> Hmm, a user named @, or what? > > > > Yes, a bogus user: > > > > "@" "" "" > > Mph. We really ought to fix things so that a quoted @ doesn't > get taken as an include file reference. Odd that it's never > come up before. > > Anyway, if you still have any open superuser sessions, the > best thing would be an ALTER USER RENAME. If you don't, > you'll have to resort to manually editing the pg_auth file, > and then rename the user as soon as you can get in. Killed the stuck postmaster with sigkill, edited the file, restarted postmaster, and it re-wrote the file with the bogus entry. I don't have any superuser sessions open. Is there another route? Ed -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
