Jonah H. Harris wrote:
On 8/9/06, Tom Lane <[EMAIL PROTECTED]> wrote:
UPDATE tries to place the new tuple on the same page it's already
on.
I think he meant for INSERT.
Right. Update is indeed taken care of already.
One example where this would help would be a customer_history table that
stores all transactions of a customer. Primary key is (customer_id,
transaction_id). You would want to keep the table clustered by
customer_id to make it quick to retrieve all transactions of a customer.
In general, any table with more or less random insert/delete activity
that you want to keep in order would benefit.
- Heikki
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
