Re: HELP pls - Mailing list pgsql-bugs

From Tom Lane
Subject Re: HELP pls
Date
Msg-id 14117.1208970659@sss.pgh.pa.us
Whole thread Raw
In response to Re: HELP pls  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: HELP pls
List pgsql-bugs
Alvaro Herrera <alvherre@commandprompt.com> writes:
> spol@mail.ru wrote:
>> I don't know how, but i got 2 postgres users.

> You've got transaction wraparound problems.  Start here:

Vacuuming isn't gonna help though.  The tuple at (0,2) has been frozen,
which means that vacuum has certainly been run on the table since the
update; so he's wrapped around so far that vacuum doesn't think it can
remove the (0,1) tuple.

I assume the OP is just trying to dump this database so he can upgrade
to something remotely modern.  It might work to change the second
tuple's usesysid to something else (eg, 2) so that pg_dump doesn't
see multiple rows matching other objects' owner fields.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Vladimir Kanazir
Date:
Subject: Re: BUG #4125: Strange ALTER TABLE behavior
Next
From: "Peter Koczan"
Date:
Subject: BUG #4126: KRB5/GSSAPI authenication fails for multipart kerberos principals