Re: Stats not updated after rollback -- autovacuum confused.

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Dawid Kuroczko <qnex42(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Stats not updated after rollback -- autovacuum confused.
Date: 2007-06-11 02:06:32
Message-ID: 200706110206.l5B26Wt19159@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Removed.

---------------------------------------------------------------------------

Alvaro Herrera wrote:
> Bruce Momjian escribi?:
> >
> > This has been saved for the 8.4 release:
> >
> > http://momjian.postgresql.org/cgi-bin/pgpatches_hold
>
> FWIW this has been fixed in 8.3, you can drop the item from the 8.4
> queue. Thanks.
>
>
> > ---------------------------------------------------------------------------
> >
> > Dawid Kuroczko wrote:
> > > Hello, I have a system where there are mostly COPYs,
> > > which insert data into a table. Ocasionally a COPY will fail (and thus,
> > > dead rows appear), but as far as I can tell ROLLBACK is not reflected
> > > anywhere in the pg_stats_user_tables. And since there are no rows
> > > n_tup_upd or n_tup_del, therefore autovacuum will not fire for that table.
>
>
> --
> Alvaro Herrera http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-06-11 02:07:05 Re: Stats not updated after rollback -- autovacuum confused.
Previous Message Alvaro Herrera 2007-06-11 01:44:49 Re: Stats not updated after rollback -- autovacuum confused.