Mike Nolan <[EMAIL PROTECTED]> writes:
>> 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.
> Unle
> 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.
Unless that field is part of the key, I wouldn't
"Keith Bottner" <[EMAIL PROTECTED]> 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
Title: Message
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 1s). This inform
