Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] WAL logging freezing

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>,"Simon Riggs" <simon(at)2ndquadrant(dot)com>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] WAL logging freezing
Date: 2006-11-03 10:40:14
Message-ID: E1539E0ED7043848906A8FF995BDA579017BFFCC@m0143.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> Seems like either we go back to ignoring non-connectable 
> databases (with the risks that entails), or adopt some 
> more-aggressive policy for launching autovacuums on them, or

Um, I think we would want to still have the ability to not need to
frequently vacuum known frozen databases.

Could we set datvacuumxid to frozenxid after freezing template0
and making it non-connectable ? There was discussion about making 
a non-connectable db connectable, one step would be to set datvacuumxid
to currentxid.

Then the rule would be: ignore db's that have datvacuumxid == frozenxid.
(only readonly db's would be allowed to have datvacuumxid == frozenxid)

Andreas

PS: I agree that the rename from datfrozenxid to datvacuumxid should be
undone

In response to

Responses

pgsql-hackers by date

Next:From: Bernd HelmleDate: 2006-11-03 11:23:23
Subject: Bug in WAL backup documentation
Previous:From: Magnus HaganderDate: 2006-11-03 09:38:32
Subject: Re: Design Considerations for New Authentication Methods

pgsql-patches by date

Next:From: Bernd HelmleDate: 2006-11-03 11:23:23
Subject: Bug in WAL backup documentation
Previous:From: Tom LaneDate: 2006-11-03 07:18:10
Subject: Re: Micro-doc patch for CREATE FUNCTION

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group