X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id EBC1B9DC819 for ; Tue, 20 Dec 2005 13:03:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17170-03 for ; Tue, 20 Dec 2005 13:03:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from alvh.no-ip.org (201-220-123-7.bk10-dsl.surnet.cl [201.220.123.7]) by postgresql.org (Postfix) with ESMTP id 31F829DC816 for ; Tue, 20 Dec 2005 13:03:29 -0400 (AST) Received: by alvh.no-ip.org (Postfix, from userid 1000) id 481ABC348F6; Tue, 20 Dec 2005 14:03:46 -0300 (CLST) Date: Tue, 20 Dec 2005 14:03:46 -0300 From: Alvaro Herrera To: Donald Fraser Cc: "[ADMIN]" Subject: Re: WITH SYSID feature dropped Message-ID: <20051220170345.GB11637@surnet.cl> Mail-Followup-To: Donald Fraser , "[ADMIN]" References: <011501c60578$47642e40$0264a8c0@demolish1> <29845.1135094224@sss.pgh.pa.us> <012201c60583$4a832080$0264a8c0@demolish1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <012201c60583$4a832080$0264a8c0@demolish1> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=3.166 required=5 tests=[AWL=-1.867, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_POST=1.44, RCVD_IN_XBL=3.114] X-Spam-Score: 3.166 X-Spam-Level: *** X-Archive-Number: 200512/228 X-Sequence-Number: 19948 Donald Fraser wrote: > We developed and have been using since 7.1, and currently running 7.4, > bespoke client / database software. The ability to manage users and security > was of high priority and we therefore developed a much more elaborate user > definition where by the information about users was held in our own tables > and we could create a postgresql database user from this table at any time. > To simplify things we controlled the SYSID and used this as the key for > mapping a postgresql user to a user defined in our table. Why not do it the other way around? Create the Postgres user first, grab its Oid, then use that as primary key in your user table. On the other hand, it's possible that the new role management in 8.1, which has brought much more elaborate privilege handling, could have rendered your user handling unnecessary. Have you considered exploring that? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support