Re: Transaction ID wraparound: problem and proposed solution

From: Jan Wieck <janwieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction ID wraparound: problem and proposed solution
Date: 2000-11-07 19:30:31
Message-ID: 200011071930.OAA01047@jupiter.jw.home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> writes:
> > Required frequency of *successful* vacuum over *all* tables.
> > We would have to remember something in pg_class/pg_database
> > and somehow force vacuum over "too-long-unvacuumed-tables"
> > *automatically*.
>
> I don't think this is a problem now; in practice you couldn't possibly
> go for half a billion transactions without vacuuming, I'd think.

ISTM you forgot that the XID counter (and usage) is global.

You need to have *any* table of *any* database in the
instance vacuumed before you are sure. Some low-traffic DB's
might not get vacuumed for years (for example template1).

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-07 19:35:45 Re: AW: AW: Issue NOTICE for attempt to raise lock level?
Previous Message Mikheev, Vadim 2000-11-07 19:26:57 RE: AW: AW: Issue NOTICE for attempt to raise lock leve l?