From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vlad Romascanu <vromascanu(at)accurev(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Any plans to expose publicly (via stored proc) relation_needs_vacanalyze, or some flavour of do_autovacuum? |
Date: | 2010-09-14 02:01:51 |
Message-ID: | 23577.1284429711@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Vlad Romascanu <vromascanu(at)accurev(dot)com> writes:
> The logical, amended solution would then be to have the "writer"
> session perform, after INSERTion but before COMMITTing, the same
> calculation that the autovacuum daemon currently performs inside
> relation_needs_vacanalyze, based on the same configuration parameters
> that the autovacuum daemon uses, before deciding whether to explicitly
> ANALYZE or not the affected application tables. Ideally one would not
> want to duplicate the relation_needs_vacanalyze logic (not to mention
> having to guess the value of last_anl_tuples, which is not exposed via
> any storedproc -- one would have to assume that it is more or less
> equivalent to pg_class.reltuples.)
I don't know if you actually looked at that code, but it's driven off of
statistics counters that are only updated at commit; and furthermore are
maintained in a different process altogether. So what you have in mind
isn't going to work ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | 夏武 | 2010-09-14 03:02:22 | Re: Help! pg_dump: Error message from server: ERROR: cache lookup failed for type 19 |
Previous Message | Craig Ringer | 2010-09-14 01:58:56 | Re: Post Install / Secure PostgreSQL |