From: | "Robert A(dot) Klahn" <robert(at)kint(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Artificially increase TransactionID? |
Date: | 2007-10-11 17:43:04 |
Message-ID: | C0C03C3A-9590-4A27-A65E-0DDB8C4C01DF@kint.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Works perfectly. I did need to artificially create pg_clog segments.
Tom: Thanks for the quick response.....
Bob.
On Oct 10, 2007, at 8:46 PM, Tom Lane wrote:
> "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 | Trevor Talbot | 2007-10-11 17:48:16 | Re: Timezone database changes |
Previous Message | Joshua D. Drake | 2007-10-11 16:56:21 | Re: Some questions about mammoth replication |