From: Pavan Deolasee <pavan.deolasee@gmail.com>
To: Gauri Kanekar <meetgaurikanekar@gmail.com>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Tue, 29 Apr 2008 16:55:38 +0530
Message-ID: <2e78013d0804290425n402f5e94i90bc7206aeefffdc@mail.gmail.com> (raw)
In-Reply-To: <7e4ba9550804290405i4c0d3a57x1640239c9995c13@mail.gmail.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
<a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com>
<7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com>
<20080428162243.GN2970@commandprompt.com>
<7e4ba9550804282246p73c62fc6y5e7cb7dda55a6b50@mail.gmail.com>
<Pine.GSO.4.64.0804290347560.20575@westnet.com>
<7e4ba9550804290405i4c0d3a57x1640239c9995c13@mail.gmail.com>
On Tue, Apr 29, 2008 at 4:35 PM, Gauri Kanekar
<meetgaurikanekar@gmail.com> wrote:
>
> Do we need to do any special config changes or any other setting for HOT to
> work??
No. HOT is enabled by default, on all tables. There is no way and need
to disable it.
>
> Any special guideline to follow to make HOT working??
>
You can do couple of things to benefit from HOT.
1. HOT addresses a special, but common case where UPDATE operation
does not change any of the index keys. So check if your UPDATE changes
any of the index keys. If so, see if you can avoid having index
involving that column. Of course, I won't advocate dropping an index
if it would drastically impact your frequently run queries.
2. You may leave some free space in the heap (fillfactor less than
100). My recommendation would be to leave space worth of one row or
slightly more than that to let first UPDATE be an HOT update.
Subsequent UPDATEs in the page may reuse the dead row created by
earlier UPDATEs.
3. Avoid any long running transactions.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pavan.deolasee@gmail.com, meetgaurikanekar@gmail.com, gsmith@gregsmith.com
Subject: Re: Replication Syatem
In-Reply-To: <2e78013d0804290425n402f5e94i90bc7206aeefffdc@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox