[EMAIL PROTECTED] writes:
I'd find all this much easier to reason about if I understood how
the versions of a row are organized and accessed. How does postgresql
locate the correct version of a row?
It doesn't, particularly. A seqscan will of course visit all the
versions of a row, and an
[EMAIL PROTECTED] wrote:
But that raises an interesting idea. Suppose that instead of one
summary row, I had, let's say, 1000. When my application creates
an object, I choose one summary row at random (or round-robin) and update
it. So now, instead of one row with many versions, I have 1000 with
Hi,
- Original Message -
From: Richard Huxton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Scott Marlowe [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, June 10, 2004 8:03 AM
Subject: Re: [GENERAL] Postgresql vs. aggregates
[EMAIL PROTECTED] wrote:
But that raises an interesting
