pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Milen A. Radev <milen@securax.org>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: Too frequent warnings for wraparound failure
Date: Thu, 10 Mar 2005 11:21:50 -0500
Message-ID: <15542.1110471710@sss.pgh.pa.us> (raw)
In-Reply-To: <14861.1110466606@sss.pgh.pa.us>
References: <42301107.6010901@securax.org>
	<14861.1110466606@sss.pgh.pa.us>

I wrote:
> "Milen A. Radev" <milen@securax.org> writes:
>> I review the log every morning. In the beginning I got "wraparound
>> failure" warnings every third day. But from a week I got those warnings
>> every day. Well we have one table in one database where there are a lot
>> of inserts, but not that many - around 30-40 thousand per day.

> Are you really doing half a billion transactions a day?

I thought of another mechanism that wouldn't require such a preposterous
load, only half a billion transactions since initdb.  (How old is this
installation, anyway, and which PG version?)

If you are creating new databases every day and you do it by cloning
template0, then the new databases would come into existence with 
datfrozenxid equal to template0's.  Once template0 is more than half a
billion transactions old, you'd start seeing the warning.

This is relatively harmless, but probably we should try to mask it.
We could make CREATE DATABASE set datfrozenxid to current time when
cloning a database that has datallowconn false, on the assumption that
the source DB is entirely frozen and so there's nothing to vacuum yet.

			regards, tom lane



view thread (14+ messages)  latest in thread

Message-ID: <15542.1110471710@sss.pgh.pa.us>
Permalink:  ../15542.1110471710@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15542.1110471710@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, milen@securax.org, pgsql-hackers@postgresql.org
  Subject: Re: Too frequent warnings for wraparound failure
  In-Reply-To: <15542.1110471710@sss.pgh.pa.us>
  References: <42301107.6010901@securax.org> <14861.1110466606@sss.pgh.pa.us> <15542.1110471710@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox