Re: [PATCHES] WAL logging freezing - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: [PATCHES] WAL logging freezing
Date
Msg-id E1539E0ED7043848906A8FF995BDA579017BFFCC@m0143.s-mxs.net
Whole thread Raw
In response to Re: [PATCHES] WAL logging freezing  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] WAL logging freezing  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
> 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


pgsql-hackers by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: Design Considerations for New Authentication Methods
Next
From: Alvaro Herrera
Date:
Subject: Re: [PATCHES] WAL logging freezing