From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Avoid losing track of data for shared tables in pgstats. |
Date: | 2007-06-07 22:09:36 |
Message-ID: | 20070607220936.GA13687@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Gregory Stark wrote:
>
> "Alvaro Herrera" <alvherre(at)postgresql(dot)org> writes:
>
> > Log Message:
> > -----------
> > Avoid losing track of data for shared tables in pgstats. Report by Michael
> > Fuhr, patch from Tom Lane after a messier suggestion by me.
>
> When does this bug date to?
It was in 8.1. I didn't verify whether it affects on 8.0; I think we
separated the shared tables in pgstats in 8.1, with the advent of
autovacuum, so I assume it doesn't. The patch doesn't apply cleanly to
8.0 anyway, and I decided not to spent much time on it seeing that
nobody has noticed it in years.
> is it possible it's related to the performance drop immediately
> following a vacuum analyze we've been seeing?
I don't think so, unless you were counting on pgstats data of shared
tables for something. The optimizer, for one, doesn't, so I doubt it
would affect query planning. And it would only affect you if your
queries were using shared tables, which I very much doubt ...
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-06-07 22:46:17 | Re: [COMMITTERS] pgsql: Avoid losing track of data for shared tables in pgstats. |
Previous Message | Tom Lane | 2007-06-07 21:46:00 | pgsql: Redefine IsTransactionState() to only return true for |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-06-07 22:10:06 | Re: little PITR annoyance |
Previous Message | Simon Riggs | 2007-06-07 21:23:06 | Re: [ADMIN] Attempt to re-archive existing WAL logsafterrestoringfrom backup |