Re: autoanalyze criteria

From: Stefan Andreatta <s(dot)andreatta(at)synedra(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: autoanalyze criteria
Date: 2013-02-25 06:23:40
Message-ID: 512B036C.4060601@synedra.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 02/24/2013 12:52 PM, Alban Hertroys wrote:
> On Feb 23, 2013, at 14:11, Stefan Andreatta <s(dot)andreatta(at)synedra(dot)com
> <mailto:s(dot)andreatta(at)synedra(dot)com>> wrote:
>
>> And we are still missing a number for rows updated since the last
>> analyse.
>
> In MVCC an update is an insert + delete, so you already got those numbers.
>
Good point. But because they are an update and a delete, they cancel
each other out and do not show up in pg_stat_user_tables.n_live_tup -
and that's the only value for which we have a reference value from the
time of the last analyze (pg_class.reltuples).

On the other hand, I might again miss something out. I would be most
happy if anybody could come up with a query to estimate autoanalyze
trigger conditions from the values we have available now.

Stefan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2013-02-25 08:00:13 Re: autoanalyze criteria
Previous Message Michael Paquier 2013-02-25 04:16:10 Re: [JDBC] can't access through SSL

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2013-02-25 06:30:12 Re: Enabling Checksums
Previous Message Adrian Klaver 2013-02-25 03:17:33 Re: Floating point error