| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Dave Thompson <dthomp325(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: fill factor guestimate |
| Date: | 2011-06-19 02:46:32 |
| Message-ID: | BANLkTi=jp_RBgBzp3b_eDucSbf-HL_hYwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jun 18, 2011 at 6:12 PM, Dave Thompson <dthomp325(at)gmail(dot)com> wrote:
> Hi,
>
> I have a table that will be updated frequently. Each row will be
> updated at least once during it's lifetime, and most rows will be
> updated ~10 times in their first 2 weeks of existence, and then
> relatively rarely after that. The rows are being updated by a prepared
> statement that gets executed with ~100 - ~600 different parameter
> sets, each one updating a single row. What should my initial
> best-guess fill-factor for the table be? Most of the updates don't
> touch an indexed column, so I'm hoping to take advantage of the HOT
> update feature. Will EXPLAIN tell me if an UPDATE uses HOT?
No but you can monitor pg_stat_user_tables to see how many updates
were HOT updates.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2011-06-19 04:03:53 | Re: Referencing function value inside CASE..WHEN |
| Previous Message | lover boi | 2011-06-19 02:45:12 | Referencing function value inside CASE..WHEN |