Re: Please HELP - URGENT - transaction wraparound error - Mailing list pgsql-general

From John Sidney-Woollett
Subject Re: Please HELP - URGENT - transaction wraparound error
Date
Msg-id 436513E9.7050503@wardbrook.com
Whole thread Raw
In response to Re: Please HELP - URGENT - transaction wraparound error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Please HELP - URGENT - transaction wraparound error  (Martijn van Oosterhout <kleptog@svana.org>)
Re: Please HELP - URGENT - transaction wraparound error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hmm. I'm pretty sure that database mail_lxtreme was unused (no
connections/activity) - I didn't think that it would need to be vacuumed
at all...

Just out of curiousity would the wraparound error (for mail_lxtreme)
actually have affected data in bp_live?

Could I just have deleted mail_lxtreme and then continued to use bp_live
as though nothing had happened?

Or had database bp_live already been damaged by the wraparound?

Thanks for your great help/advice - it's much appreciated.

John

Tom Lane wrote:
> John Sidney-Woollett <johnsw@wardbrook.com> writes:
>
>>OK, I restored the pgsql/data to another server and started up postgres
>>and this is what I got:
>
>
>>  SELECT datname, age(datfrozenxid) FROM pg_database;
>>    datname    |     age
>>--------------+-------------
>>  mail_lxtreme | -2074187459
>>  bp_live      |  1079895636
>>  template1    |  1076578064
>>  template0    | -2074187459
>>(4 rows)
>
>
>>mail_lxtreme is a test mail db and I don't care about it. So it could
>>have been deleted without any worries...
>
>
>>Which databases are a problem? Is it template0 or bp_live and template1?
>
>
> mail_lxtreme is exactly the problem.  You weren't vacuuming it...
>
> (template0 is a special case and can be ignored.)
>
>             regards, tom lane

pgsql-general by date:

Previous
From: psql@dgrmm.net
Date:
Subject: create table in transaction fails
Next
From: Martijn van Oosterhout
Date:
Subject: Re: create table in transaction fails