Kristaps Armanis <[EMAIL PROTECTED]> writes:
> Is there any solution?
I think what you have to do is use pg_resetxlog with -x and a value just shy
of 2^32. then pg_dump and restore into a fresh database. I've never done it
though so perhaps you should wait until someone with more experience spea
Friday, January 21, 2005, 5:30:07 PM, Jus rakstijat:
MvO> Looks like XID wraparound, you hit the 4 billion transaction mark. This
MvO> was fixed in 7.2 IIRC. Unfortunatly I don't know of an easy way to
MvO> recover, but this should give you something to search the archives for.
Till how sorted th
On Fri, Jan 21, 2005 at 03:33:28PM +0200, Kristaps Armanis wrote:
> Last night no crash, not anything, just @ one moment all records for
> last year where gone, all ros created for last year & tables created
> while this time - and not in only one database, but all 6 DB's on this
> server.
Looks l
Greetings,
Some really strange things happened here. We were using old 7.1
postgres on 2.4 linux and db files living on ext3 partition for some time,
vacuuming regulary and not upgrading only because software didn't worked with
7.2+.
(developers where in progress, but not yet).
Last night no cra