| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(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-14 02:48:22 |
| Message-ID: | 2e78013d0807131948g823d740t10f5f1513cd6a2e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jul 12, 2008 at 2:25 AM, Roberts, Jon <Jon(dot)Roberts(at)asurion(dot)com> wrote:
>>
>> --
>
> 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
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J Ottery | 2008-07-14 02:57:17 | Restoring Database from Data directory backup. |
| Previous Message | Danyelle Gragsone | 2008-07-14 02:22:54 | Re: REQUIREMENTS FOR POSTGRESQL DATABASE |