Re: In-core regression tests for replication, cascading, archiving, PITR, etc.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.
Date: 2013-12-02 16:25:08
Message-ID: 20131202162508.GA5731@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane escribió:

> When I've wanted to do that in the past, I've used pg_resetxlog to
> adjust a cluster's counters. It still requires some manual hacking
> though because pg_resetxlog isn't bright enough to create the new
> pg_clog files needed when you move the xid counter a long way.
> We could fix that, or we could make the backend more forgiving of
> not finding the initial clog segment present at startup ...

FWIW we already have some new code that creates segments when not found.
It's currently used in multixact, and the submitted "commit timestamp"
module uses it too.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-12-02 16:41:10 Re: [GENERAL] pg_upgrade ?deficiency
Previous Message Robert Haas 2013-12-02 16:11:48 Re: Add full object name to the tag field