| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| 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 01:44:49 |
| Message-ID: | 20070611014449.GA7661@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-06-11 02:06:32 | Re: Stats not updated after rollback -- autovacuum confused. |
| Previous Message | Tom Lane | 2007-06-11 01:21:05 | What's with the StartDb:2 failures on skylark? |