| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Gordon Shannon <gordo169(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Help writing a query to predict auto analyze |
| Date: | 2010-05-20 03:45:32 |
| Message-ID: | 1274326933-sup-9169@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Excerpts from Gordon Shannon's message of mié may 19 23:32:07 -0400 2010:
>
> alvherre wrote:
> >
> > n_live_tup and n_dead_tup corresponds to the current numbers,
> > whereas "last analysis tuples" are the values from back when the
> > previous analyze ran. These counters keep moving per updates, deletes,
> > inserts, they are not static.
>
> OK. Do you know how can I get the values from back when the previous
> analyze ran?
I don't think we expose those values to SQL. I guess you could create a
C function to get it, modelled after pg_stat_get_live_tuples and friends
(see src/backend/utils/adt/pgstatfuncs.c).
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Walker | 2010-05-20 06:19:17 | How to lose transaction history (xmin values, WAL, etc.)? |
| Previous Message | Gordon Shannon | 2010-05-20 03:32:07 | Re: Help writing a query to predict auto analyze |