X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B41578B9FDF for ; Fri, 4 Feb 2005 23:09:42 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 54200-07 for ; Fri, 4 Feb 2005 23:09:31 +0000 (GMT) Received: from entiat.olympus.net (entiat.olympus.net [65.117.224.69]) by svr1.postgresql.org (Postfix) with ESMTP id C3C4D8B9F34 for ; Fri, 4 Feb 2005 23:09:32 +0000 (GMT) Received: from LoricaMail on entiat.olympus.net ([172.21.2.55] helo=entiat.olympus.net) by entiat.olympus.net with esmtp (Exim 4.42) id 1CxCZw-0004NK-La for pgsql-admin@postgresql.org; Fri, 04 Feb 2005 15:09:32 -0800 Received: from tuk-dsl-226-242.olympus.net ([65.117.226.242]:33773 helo=[192.168.0.5]) by entiat.olympus.net with esmtpa (Exim 4.42) id 1CxCZq-0004Lz-12 for pgsql-admin@postgresql.org; Fri, 04 Feb 2005 15:09:26 -0800 Message-ID: <420400A5.3000608@olympus.net> Date: Fri, 04 Feb 2005 15:09:25 -0800 From: Michael Klatt User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: pgsql-admin@postgresql.org Subject: Re: Recovery using Online Backup+WAL and broken passwords References: <4203A249.1010409@olympus.net> <15237.1107536658@sss.pgh.pa.us> In-Reply-To: <15237.1107536658@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virtual-Service: OlympusNet X-Exim-Id: 1CxCZq-0004Lz-12 X-Olympus-MailID-CF: 1CxCZq-0004Lz-12Feb04150926fkg X-Olympus-Virus: Scanned X-Olympus-OlympusNet: Initial processing complete X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/58 X-Sequence-Number: 16226 Tom Lane wrote: > [ thinks about that... ] Hmm, you're right, there is no mechanism to > cause the flat password file to be rebuilt after a restore. So newly > created users won't be in it (and for that matter it won't reflect > post-backup password changes for existing users). Just (re)assign any > one user's password and things should be ok. Great, this gives me a great short-term work-around solution to the problem. I've verified that setting any user password automatically fixes all of them. Do you think a fix will show up in 8.0.2? Thanks! Michael