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 E622B9DCA85 for ; Tue, 20 Dec 2005 12:59:56 -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 17493-01 for ; Tue, 20 Dec 2005 12:59:55 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 60CE39DCA61 for ; Tue, 20 Dec 2005 12:59:54 -0400 (AST) 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 jBKGxno3000526; Tue, 20 Dec 2005 11:59:49 -0500 (EST) To: "Donald Fraser" cc: "[ADMIN]" Subject: Re: WITH SYSID feature dropped In-reply-to: <012201c60583$4a832080$0264a8c0@demolish1> References: <011501c60578$47642e40$0264a8c0@demolish1> <29845.1135094224@sss.pgh.pa.us> <012201c60583$4a832080$0264a8c0@demolish1> Comments: In-reply-to "Donald Fraser" message dated "Tue, 20 Dec 2005 16:34:43 +0000" Date: Tue, 20 Dec 2005 11:59:49 -0500 Message-ID: <525.1135097989@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.022 required=5 tests=[AWL=0.022] X-Spam-Score: 0.022 X-Spam-Level: X-Archive-Number: 200512/227 X-Sequence-Number: 19947 "Donald Fraser" writes: > Yes we do have another use. > 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. It's not apparent to me why you have to control the userID in order to have an auxiliary table defining a user. You could do something like keeping the currently assigned OID in the aux table, setting the field to null or zero if the user doesn't currently exist in pg_authid. > I take it then that the patching of that feature would cause problems > because the OID is controlled by postgreql and we could therefore be trying > to create a user with an OID that could already be in use. You ran that risk already with the SYSID scheme, no? regards, tom lane