From: Tom Lane <tgl@sss.pgh.pa.us>
To: Keith Bottner <kbottner@comcast.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: What's faster?
Date: Fri, 26 Dec 2003 19:49:07 -0500
Message-ID: <8602.1072486147@sss.pgh.pa.us> (raw)
In-Reply-To: <008301c3cc0d$f3f337b0$7d00a8c0@juxtapose>
References: <008301c3cc0d$f3f337b0$7d00a8c0@juxtapose>
"Keith Bottner" <kbottner@comcast.net> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, kbottner@comcast.net
Subject: Re: What's faster?
In-Reply-To: <8602.1072486147@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox