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 58E82D1B432 for ; Sat, 27 Dec 2003 00:49:54 +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 60019-09 for ; Fri, 26 Dec 2003 20:49:08 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E5A76D1B449 for ; Fri, 26 Dec 2003 20:49:04 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hBR0n719008603; Fri, 26 Dec 2003 19:49:07 -0500 (EST) To: "Keith Bottner" Cc: pgsql-performance@postgresql.org Subject: Re: What's faster? In-reply-to: <008301c3cc0d$f3f337b0$7d00a8c0@juxtapose> References: <008301c3cc0d$f3f337b0$7d00a8c0@juxtapose> Comments: In-reply-to "Keith Bottner" message dated "Fri, 26 Dec 2003 18:11:19 -0600" Date: Fri, 26 Dec 2003 19:49:07 -0500 Message-ID: <8602.1072486147@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/299 X-Sequence-Number: 5159 "Keith Bottner" writes: > 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, Very likely a good idea, if the primary key that you'd need to add to identify the balance is narrow. Hard to say exactly how large the benefit would be, but I'd think the update costs would be reduced considerably. regards, tom lane