X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 994A3D8514 for ; Mon, 29 Aug 2005 22:29:29 -0300 (ADT) 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 57324-09 for ; Tue, 30 Aug 2005 01:29:26 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3E5A9D850C for ; Mon, 29 Aug 2005 22:29:24 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j7U1TPKn015889; Mon, 29 Aug 2005 21:29:27 -0400 (EDT) To: Jason Stone Cc: pgsql-admin@postgresql.org Subject: Re: password authentication with external passwd file In-reply-to: <20050829174059.F2358@treehorn.dfmm.org> References: <20050827001001.L70885@treehorn.dfmm.org> <20050827133049.GA59344@winnie.fuhr.org> <20050829174059.F2358@treehorn.dfmm.org> Comments: In-reply-to Jason Stone message dated "Mon, 29 Aug 2005 17:49:31 -0700" Date: Mon, 29 Aug 2005 21:29:25 -0400 Message-ID: <15888.1125365365@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200508/376 X-Sequence-Number: 18695 Jason Stone writes: > out of curiosity, why was the secondary password file capability removed? You'd have to look into the pghackers archives for details, but my recollection is that it didn't play nicely with other features that we wanted to add. > I really liked the simplicity of being able to manage users completely > outside of the database, and to be able to do maintainence on the user > accounts without the database's even running. This is rather an overstatement. You were able to change their passwords externally, perhaps, but that's a pretty limited form of "management". regards, tom lane