From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Michal Vitecek <fuf(at)mageo(dot)cz>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: updating a row in a table with only one row |
Date: | 2009-10-02 18:18:38 |
Message-ID: | b42b73150910021118p69484576y2f044b25c89d42c9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, Oct 2, 2009 at 1:39 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Oct 2, 2009 at 9:54 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>> it is ridiculous. your problem is almost definitely dead rows. I
>> can't recall (and I can't find the info anywhere) if the 'hot' feature
>> requires an index to be active -- I think it does. If so, creating a
>> dummy field and indexing it should resolve the problem. Can you
>> confirm the dead row issue by doing vacuum verbose and create the
>> index? please respond with your results, I'm curious. Also, is
>> autovacuum on? Have you measured iowait?
>
> Since he's updating all the fields in the table, an index will
> certainly ensure that HOT does not apply, no?
you're right...I missed that he put an index on value5 (why?). That's
what's killing him.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-10-02 18:38:50 | Re: updating a row in a table with only one row |
Previous Message | Greg Smith | 2009-10-02 17:43:40 | Re: Best suiting OS |