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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-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

Browse pgsql-hackers by date

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

Browse pgsql-patches by date

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