X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C5663474E5C for ; Wed, 26 Feb 2003 08:04:48 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 46130-09 for ; Wed, 26 Feb 2003 08:04:38 -0500 (EST) Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by postgresql.org (Postfix) with SMTP id 09926474E42 for ; Wed, 26 Feb 2003 08:04:37 -0500 (EST) Received: (qmail 25502 invoked by uid 0); 26 Feb 2003 13:04:39 -0000 Date: Wed, 26 Feb 2003 14:04:39 +0100 (MET) From: daniel alvarez To: pgsql-performance@postgresql.org MIME-Version: 1.0 Subject: X-Priority: 3 (Normal) X-Authenticated-Sender: #0002681999@gmx.net X-Authenticated-IP: [217.6.136.218] Message-ID: <1859.1046264679@www36.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/209 X-Sequence-Number: 1265 In some older mails in the archive I found rumors about difficulcies that might occur when OIDs are used as an integral part of a data model. I am considering the option of placing an index on the already existing oid and using it as the primary key for all tables (saves some space and a sequence lookup). This includes saving the oid in foreign keys (virtual ones, not actually declared references). I read that using OID in keys is generally a bad idea. Is it really? Why exactly? Are there any disadvantages as to reliability or performance apart from accidentally forgetting to use the -o option with pg_dump? If so, please give details. I felt especially worried by a postgres developer's statement in another archived mail: "As far as I know, there is no reason oid's have to be unique, especially if they are in different tables." (http://archives.postgresql.org/pgsql-hackers/1998-12/msg00570.php) How unique are oids as of version 7.3 of postgres ? Is it planned to keep oids semantically the same in future releases of postgres? Will the oid type be extended so that oids can be larger than 4 bytes (if this is still correct for 7.3) and do not rotate in large systems? Thanks for your time and advice. Daniel Alvarez =20 =20 --=20 +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte l=E4cheln! Fotogalerie online mit GMX ohne eigene Homepage!