public inbox for [email protected]
help / color / mirror / Atom feedFrom: Harry <[email protected]>
To: [email protected]
Subject: Re: Database Recovery
Date: Sun, 19 Dec 2004 17:08:42 -0800 (PST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
--- Alvaro Herrera <[email protected]> wrote:
> > http://www.hjackson.org/blog/archives/2004/12/postgresql_data.html
>
> Huh, this sounds like transaction Id wraparound to me. Do you
> regularly run vacuums on the whole database? Did you ask for expert
> help on the lists before running to do whatever you did?
I didn't run to do anything ;) I had a good think and a good google
before I done anything and I have all my data back because of it.
Luckily for me the data was neither life or job threatening so I was
able to take a few more risks than necessary. I was actually
volunteering to write the database recovery section of the docs, not
asking for help.
As per TID wraparound. I have been lucky enough never to have received
anything similar to the following warning (taken from 7.4 docs)
play=# vacuum;
WARNING: Some databases have not been vacuumed in 1613770184
transactions.
Better vacuum them within 533713463 transactions,
or you may have a wraparound failure.
VACUUM
you will also notice that I used a TID of less than 100 million to
recover the database. I was nowhere near 0.5 billion as recommended by
the docs.
Harry
=====
Harry
Join team plico.
http://www.hjackson.org/cgi-bin/folding/index.pl
__________________________________
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Database Recovery
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox