Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5DEOpE28870 for ; Wed, 13 Jun 2001 10:24:51 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f5DEOh026259; Wed, 13 Jun 2001 10:24:43 -0400 (EDT) To: Nicolas Kowalski cc: pgsql-admin@postgresql.org Subject: Re: User rights In-reply-to: References: Comments: In-reply-to Nicolas Kowalski message dated "Wed, 13 Jun 2001 15:33:26 +0200" Date: Wed, 13 Jun 2001 10:24:43 -0400 Message-ID: <26256.992442283@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/77 X-Sequence-Number: 1632 Nicolas Kowalski writes: > The problem is, if a user tries to authenticate and is not in the > pg_shadow system table but *is* in the passwd file, the access will > always fail. If the user appears in the pg_shadow table, no problems. If you're not in pg_shadow you are not a postgres user. Bogus entries in password files won't help you. > By mistake, I deleted a user (me in fact) from the pg_shadow table. I > was the owner of several tables. As a superuser, I re-created the user, > with the same information, sysid included. But now, I am unable to > manage or even do some SELECT on the table I was the owner. I checked > the relowner field in the pg_class table, and it has the value of my > sysid... Hmm, that should work, if you're sure you got the right sysid. Also check to make sure there is only one row in pg_shadow with that sysid. regards, tom lane