| From: | Colin Taylor <colin(dot)taylor(at)gmail(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: A Tale of 2 algorithms |
| Date: | 2012-10-05 00:34:43 |
| Message-ID: | CAN6Zwvv0_Yerh7YNSHu+UmfyrOwzMGULDctkQBvqp6otgJA3Ew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Oct 2, 2012 at 5:54 PM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> wrote:
> On 10/02/2012 05:24 AM, Colin Taylor wrote:
>
>> My thoughts are: surely 0-row updates dont cause this or have impact on
>> the vacuum. I'm still doing the same updates after all why have things
>> degenerated so badly?
>>
>
> What exactly is bloating? Have you checked? Is it the table its self? One
> of its indexes? Something else?
>
> --
> Craig Ringer
>
The table and its indexes, I have them in separate tablespaces so its quite
apparent.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2012-10-05 14:06:41 | Re: how to avoid deadlock on masive update with multiples delete |
| Previous Message | Jeff Janes | 2012-10-04 16:10:08 | Re: how to avoid deadlock on masive update with multiples delete |