Re: Autovacuum versus rolled-back transactions

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Autovacuum versus rolled-back transactions
Date: 2007-05-26 10:55:03
Message-ID: 46581207.3060305@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> I'm kind of leaning to the separate-tally method and abandoning the
> assumption that the identities hold. I'm not wedded to the idea
> though. Any thoughts?

That seems like the best approach to me. Like the scan/fetch counters,
n_tup_ins and n_tup_del represent work done regardless of
commit/rollback, but n_live_tup and n_dead_tup represent the current
state of the table.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2007-05-26 13:12:14 Re: Why not keeping positions in GIN?
Previous Message Tom Lane 2007-05-25 23:49:35 Re: Role privileges in PostgreSQL.