X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E9133D1B479 for ; Sat, 27 Dec 2003 00:12:07 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 59501-07 for ; Fri, 26 Dec 2003 20:11:20 -0400 (AST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by svr1.postgresql.org (Postfix) with ESMTP id 856E1D1B43C for ; Fri, 26 Dec 2003 20:11:17 -0400 (AST) Received: from juxtapose (c-24-1-81-113.client.comcast.net[24.1.81.113]) by comcast.net (sccrmhc13) with SMTP id <2003122700111901600ro8oie>; Sat, 27 Dec 2003 00:11:19 +0000 From: "Keith Bottner" To: Subject: What's faster? Date: Fri, 26 Dec 2003 18:11:19 -0600 Message-ID: <008301c3cc0d$f3f337b0$7d00a8c0@juxtapose> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0084_01C3CBDB.A958C7B0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.6 tagged_above=0.0 required=5.0 tests=HTML_30_40 X-Spam-Level: X-Archive-Number: 200312/298 X-Sequence-Number: 5158 This is a multi-part message in MIME format. ------=_NextPart_000_0084_01C3CBDB.A958C7B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a database where the vast majority of information that is related to a customer never changes. However, there is a single field (i.e. balance) that changes potentially tens to hundreds of times per day per customer (customers ranging in the 1000s to 10000s). This information is not indexed. Because Postgres requires VACUUM ANALYZE more frequently on updated tables, should I break this single field out into its own table, and if so what kind of a speed up can I expect to achieve. I would be appreciative of any guidance offered. =20 BTW, currently using Postgres 7.3.4 =20 =20 Keith =20 =20 ------=_NextPart_000_0084_01C3CBDB.A958C7B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
I have a = database=20 where the vast majority of information that is related to a customer never= =20 changes. However, there is a single field (i.e. balance) that changes= =20 potentially tens to hundreds of times per day per customer (customers rangi= ng in=20 the 1000s to 10000s). This information is not indexed. Because Postgres req= uires=20 VACUUM ANALYZE more frequently on updated tables, should I break this singl= e=20 field out into its own table, and if so what kind of a speed up can I expec= t to=20 achieve. I would be appreciative of any guidance offered.
 
BTW, curr= ently using=20 Postgres 7.3.4
 
 
Keith
 
 
------=_NextPart_000_0084_01C3CBDB.A958C7B0--