X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B748E52945 for ; Sat, 28 May 2005 14:42:28 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 95852-02 for ; Sat, 28 May 2005 17:42:19 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id 58DD85292F for ; Sat, 28 May 2005 14:36:49 -0300 (ADT) Received: (qmail 10889 invoked from network); 28 May 2005 19:37:19 +0200 Received: from unknown (HELO localhost) (boutiquenumerique-lists@192.168.0.4) by boutiquenumerique.com with SMTP; 28 May 2005 19:37:19 +0200 To: "Andrew McMillan" , "Eric Lauzon" Cc: pgsql-performance@postgresql.org Subject: Re: OID vs overall system performances on high load References: <1117256890.30150.179.camel@lamb.mcmillan.net.nz> Message-ID: Date: Sat, 28 May 2005 19:36:42 +0200 From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <1117256890.30150.179.camel@lamb.mcmillan.net.nz> User-Agent: Opera M2(BETA2)/8.0 (Linux, build 987) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/418 X-Sequence-Number: 12582 > The OID column is an extra few bytes on each row. If you don't have any > use for it (and let's face it: most of us don't), then create your > tables "without OID". Also there are some useful hacks using the oid which don't work if it wraps around, thus preventing it from wrapping around by not using on every table could be useful in some cases...