From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
---|---|
To: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <lists(at)stringsutils(dot)com>, "Pgsql General list" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Default fill factor for tables? |
Date: | 2008-07-16 13:30:57 |
Message-ID: | 1A6E6D554222284AB25ABE3229A92762E9A7AD@nrtexcus702.int.asurion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> > I can find very little information on hot updates but I found this:
> http://archives.postgresql.org/pgsql-patches/2006-11/msg00059.php
> >
> > It states, "This design optimizies the updates when none of the
index
> columns are modified and length of the tuple remains the same after
> update."
> >
> > How can a row's length change? I think it must mean the size (in
bytes)
> of the row remains the same.
> >
>
> I bet you are looking at an old design. That has undergone many
> changes and the current implementation does not have any restriction
> about the row length changes. But a necessary condition is to have
> enough free space in the block (and of course not changing any index
> columns).
>
> You can find the latest README in the source code under
> src/backend/access/heap/README.HOT
>
I'm using 8.3.1 on Solaris and I just tried this:
CREATE TABLE test (a int) WITH (hot_update='true');
It fails with:
ERROR: unrecognized parameter "hot_update"
Is a hot update automatic in 8.3.x and that is why there isn't any
formal documentation other than what is in the source code?
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2008-07-16 13:33:56 | Re: UPDATE runs slow in a transaction |
Previous Message | David Brown | 2008-07-16 13:25:57 | 10.5 OS X ppc64 problem |