force of last XID

From: Alex Pilosov <alex(at)pilosoft(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: force of last XID
Date: 2001-05-19 03:42:47
Message-ID: Pine.BSO.4.10.10105182340360.18557-100000@spider.pilosoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I managed to drop really important table. Fortunately, I had a backup of
the table (raw #### file, not a ascii file). After putting that table into
freshly initdb'd database, postgres doesn't see new transactions even
though 'vacuum' sees the tuples alright.

So, question. I'd like to force XID (of last committed transaction) of
postgres forward. Is there a good way to do it or hacking source is the
only way?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-05-19 03:43:42 Re: Plans for solving the VACUUM problem
Previous Message Tom Lane 2001-05-19 03:38:58 Re: Interesting question