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 C955C9DC819 for ; Tue, 20 Dec 2005 12:35:32 -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 12130-07 for ; Tue, 20 Dec 2005 12:35:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by postgresql.org (Postfix) with ESMTP id 200999DC816 for ; Tue, 20 Dec 2005 12:35:30 -0400 (AST) Received: from demolish1 (82-133-115-238.dyn.gotadsl.co.uk [82.133.115.238]) by smtp.nildram.co.uk (Postfix) with SMTP id 9E2FF26FEF6 for ; Tue, 20 Dec 2005 16:34:43 +0000 (GMT) Message-ID: <012201c60583$4a832080$0264a8c0@demolish1> From: "Donald Fraser" To: "[ADMIN]" References: <011501c60578$47642e40$0264a8c0@demolish1> <29845.1135094224@sss.pgh.pa.us> Subject: Re: WITH SYSID feature dropped Date: Tue, 20 Dec 2005 16:34:43 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[AWL=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200512/225 X-Sequence-Number: 19945 ----- Original Message ----- From: "Tom Lane" > "Donald Fraser" writes: > > 1) Was there a good reason for dropping this feature? > Users/groups are identified by OIDs now, not by sysids. > > The original motivation for allowing manual assignment of userids was to > allow recovery if a user was dropped while still owning objects --- you > could recreate the user with the same sysid and then the objects' owner > fields would match up. 8.1 now does reference counting and prevents you > from dropping users who still own anything, so AFAICS that use-case is > gone. Do you have another one? 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. Obviously we have the information in our table to go from a postgresql user name back to the original SYSID but that process is messy and requires string manipulation etc. The ability to controll the SYSID, now labelled OID, basically allows for a more elaborate third-party managment of postgresql users. It is not impossible to use the postgresql user name to map into the table we have created but it would be nicer and cleaner to be able to continue using the OID. 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. Regards Donald Fraser