Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 3860F9FB554 for ; Mon, 22 Jan 2007 18:36:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 09282-05 for ; Mon, 22 Jan 2007 18:36:10 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id EEAC09FB507 for ; Mon, 22 Jan 2007 18:36:13 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-100-202.bk7-dsl.surnet.cl [200.126.100.202]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l0MMa1OJ030058; Mon, 22 Jan 2007 14:36:02 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 896E032A0E; Mon, 22 Jan 2007 19:35:57 -0300 (CLST) Date: Mon, 22 Jan 2007 19:35:57 -0300 From: Alvaro Herrera To: Peter Koczan Cc: "Jim C. Nasby" , pgsql-admin@postgresql.org Subject: Re: Upgrading to 8.2, changes in user/group management scripts Message-ID: <20070122223557.GV26006@alvh.no-ip.org> Mail-Followup-To: Peter Koczan , "Jim C. Nasby" , pgsql-admin@postgresql.org References: <4544e0330701191345l64b72722j7530db0d7d345f6f@mail.gmail.com> <20070121173854.GD77382@nasby.net> <4544e0330701221236o205ec223t7da292a1cce6bba3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4544e0330701221236o205ec223t7da292a1cce6bba3@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Mon, 22 Jan 2007 14:36:09 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/206 X-Sequence-Number: 24362 Peter Koczan wrote: > The main thing I'm worried about is the orphaned objects problem. It's not > adding users so much as removing them that I'm concerned about (I work at a > University and we remove inactive/non-enrolled users). These cases would > likely require a lot more in-depth intervention by myself and other staff. Instead of deleting stuff from pg_authid directly, use DROP ROLE. If this doesn't work because the role owns something, you may use a combination of DROP OWNED and REASSIGN OWNED. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support