Re: How to manually force a transaction wraparound - Mailing list pgsql-general

From Eric Ridge
Subject Re: How to manually force a transaction wraparound
Date
Msg-id CANcm6wZqNpaTvjbAuE8=dK199XserEX6w-_WZP_aqEx3=+nj1Q@mail.gmail.com
Whole thread Raw
In response to Re: How to manually force a transaction wraparound  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-general
On Fri, Apr 29, 2016 at 10:16 PM Thomas Munro <thomas.munro@enterprisedb.com> wrote:
On Sat, Apr 30, 2016 at 10:48 AM, Eric Ridge <eebbrr@gmail.com> wrote:
> I want to force my database to wraparound, just to see what happens.  How
> can I do this without consuming a few billion transactions?

Take a look at the script repro-bogus-subtrans-error-wraparound.sh
from this email:

http://www.postgresql.org/message-id/CAEepm=3z0EoLpo5wTUwseM38kbq+Gjp8xXiuLJkUqpM-SW7kAw@mail.gmail.com

That used pg_resetxlog -x $XID $PGDATA, but needed to do several hops
stop/pg_resetxlog/start hops to get all the way around the xid clock.

Thanks Thomas.  I ended up figuring out something similar after I read the docs on pg_resetxlog.

It did something interesting to two of my local databases, but I was able to figure out what I wanted to know.

Thanks again!

eric

pgsql-general by date:

Previous
From: "dandl"
Date:
Subject: Re: CREATE OR REPLACE AGGREGATE -- NOT!
Next
From: Steven Lembark
Date:
Subject: Trying to create array of enum to array of text for exclusion constraint