Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id VAA40211; Sat, 28 Aug 1999 21:05:06 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id VAA09801; Sat, 28 Aug 1999 21:00:46 -0400 (EDT) To: Michael Richards cc: pgsql-sql@postgreSQL.org, hackers@postgreSQL.org Subject: Re: [HACKERS] entries in pg_shadow In-reply-to: Your message of Sat, 28 Aug 1999 21:40:29 -0300 (ADT) Date: Sat, 28 Aug 1999 21:00:46 -0400 Message-ID: <9799.935888446@sss.pgh.pa.us> From: Tom Lane Michael Richards writes: > The entries entered in pg_shadow haven't ever worked for me. I've tried a > number of times without success. If I update a user in there and set a > password for them: IIRC, the only way to set a password that actually works is ALTER USER. The reason direct SQL hacking on pg_shadow doesn't work is that pg_shadow isn't what the postmaster looks at (the PM itself can't do database operations without getting into possible deadlock situations). There's a flat text file somewhere that contains the Real Info. ALTER USER and friends know to rewrite the flat file after updating pg_shadow. This is documented somewhere, I think, but not nearly prominently enough... regards, tom lane