From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: force of last XID |
Date: | 2001-05-19 03:58:52 |
Message-ID: | 200105190358.f4J3wq017477@candle.pha.pa.us |
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?
Try copying over the pg_log file from the old database. That should
help.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2001-05-19 06:21:18 | Re: Problems with avg on interval data type |
Previous Message | Bruce Momjian | 2001-05-19 03:57:01 | Re: Plans for solving the VACUUM problem |