From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Robert A(dot) Klahn" <robert(at)kint(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Artificially increase TransactionID? |
Date: | 2007-10-11 03:46:15 |
Message-ID: | 2570.1192074375@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Robert A. Klahn" <robert(at)kint(dot)org> writes:
> I am interested in increasing the PostgreSQL TransactionID, as part
> of testing a (yet another) replication system that I am working on.
> (http://bruce.codehaus.org/ for the interested). I would like to test
> what happens when the transactionID crosses 2^31 and when it wraps
> around at 2^32-1. Other than running "select now()" 2^31 times, is
> there a practical way to raise the transactionID by large amounts?
Shut down postmaster, use pg_resetxlog to set NextXID to whatever you
want, restart and test. You might need to artificially create pg_clog
and pg_subtrans segments matching the chosen starting point, but other
than that there's not a lot of memory of latest XID in the system.
Bumping it by more than 2G-less-reasonable-safety-margin is unfair of
course ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gokulakannan Somasundaram | 2007-10-11 04:58:59 | Re: Including Snapshot Info with Indexes |
Previous Message | Bruce Momjian | 2007-10-11 01:34:06 | Re: Skytools committed without hackers discussion/review |