Re: pgsql: Expose the estimation of number of changed tuples since last ana

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: cedric <cedric(at)2ndquadrant(dot)com>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Expose the estimation of number of changed tuples since last ana
Date: 2013-07-05 13:44:55
Message-ID: CABUevEwof7vb=jt3bMYnyGvF2e6axHKHnBiBfKj2-kQjDCu35g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Fri, Jul 5, 2013 at 3:43 PM, Cédric Villemain <cedric(at)2ndquadrant(dot)com> wrote:
>> Expose the estimation of number of changed tuples since last analyze
>>
>> This value, now pg_stat_all_tables.n_mod_since_analyze, was already
>> tracked and used by autovacuum, but not exposed to the user.
>
> I though you agreed on a shorter name ? (n_mod_tuple ?)

No, I suggested a shorter name, but was convinced that this would
likely be more confusing..

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2013-07-05 14:20:05 Re: [COMMITTERS] pgsql: Add new GUC, max_worker_processes, limiting number of bgworkers.
Previous Message Cédric Villemain 2013-07-05 13:43:41 Re: pgsql: Expose the estimation of number of changed tuples since last ana