Re: Frequent Update Project: Design Overview ofHOTUpdates

From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>, Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Frequent Update Project: Design Overview ofHOTUpdates
Date: 2006-11-13 12:42:26
Message-ID: 1163421745.2839.50.camel@coppola.muc.ecircle.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[snip]
> IMHO *most* UPDATEs occur on non-indexed fields. [snip]
>
> If my assumption is badly wrong on that then perhaps HOT would not be
> useful after all. If we find that the majority of UPDATEs meet the HOT
> pre-conditions, then I would continue to advocate it.

Just to confirm that the scenario is valid: our application has almost
all it's updates affecting only non-indexed columns. There are a few
exceptions, but the vast majority is non-indexed, and that holds to the
execution frequency too, not just for the count of tables/queries.

Cheers,
Csaba.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Enrico 2006-11-13 15:05:08 EAN barcode datatype
Previous Message Simon Riggs 2006-11-13 11:03:39 Re: Frequent Update Project: Design Overview ofHOTUpdates