Re: Autoanalyze and OldestXmin

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Autoanalyze and OldestXmin
Date: 2011-06-09 15:05:52
Message-ID: FD21FC80-4C2D-47D8-903D-A2E9AD9C3945@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09-Jun-2011, at 8:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Jun 9, 2011 at 10:52 AM, Pavan Deolasee
>> <pavan(dot)deolasee(at)gmail(dot)com> wrote:
>>>> I am wondering if we shouldn't be asking ourselves a different
>>>> question: why is ANALYZE running long enough on your tables for this
>>>> to become an issue? How long is it taking?
>
>>> The log file attached in the first post has the details; it's taking around 5 mins for the accounts table with 50 scale factor and 50 clients
>
>> Wow, that's slow. Still, what if the user were doing a transaction of
>> comparable size? It's not like ANALYZE is doing a gigantic amount of
>> work.
>
> I wonder what vacuum cost delay settings are in use ...
>

Default settings with 512Mb shared buffers

Thanks.
Pavan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-06-09 15:09:14 Re: release slippage
Previous Message Tom Lane 2011-06-09 14:59:54 Re: Autoanalyze and OldestXmin