-----BEGIN PGP SIGNED MESSAGE-----
On Mon, 7 Jan 2008 11:58:29 -0500 (EST)
Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > > Ah -- interesting. This is a known issue, but we haven't found a
> > > solution yet.
> > >
> > Is there bug number?
> I assume it is this TODO item:
> o Prevent long-lived temporary tables from causing frozen-xid
> advancement starvation
> The problem is that autovacuum cannot vacuum them to set
> frozen xids; only the session that created them can do that.
> but am confused how the fix worked. Have all of these backends been
> active for 1 billion transactions?
Well it certainly appears that the TODO item is related. However there
are a couple of differences.
1. I had to manually vacuum because we had already hid xidStoplimit.
2. Postgres has been restarted multiple times and it made zero
E.g; PostgreSQL isn't cleaning up after itself and it isn't apparent
when it happens.
Joshua D. Drake
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
In response to
pgsql-hackers by date
|Next:||From: Joshua D. Drake||Date: 2008-01-07 17:27:53|
|Subject: Re: VACUUM FULL out of memory|
|Previous:||From: Bruce Momjian||Date: 2008-01-07 16:58:29|
|Subject: Re: Bug: Unreferenced temp tables disables vacuum
to update xid|