/postgresql_data.html
Its a bit long winded but if there are no docs detailing various
recovery procedures and there are people willing to answer questions
and make sure I was on the right track then I would be willing to write
it?
Has it already been written? Thoughts?
=
Harry
Join team plico.
http
ed 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
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Harry <[EMAIL PROTECTED]> writes:
> > Is there any material online on how to recover a corrupt postgresql
> > database?
>
> There are dozens if not hundreds of case histories in the mailing
> list archives; the l
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Harry <[EMAIL PROTECTED]> writes:
> > In hindsight I would have done some things differently, like
> posting to
> > one of the lists. If you think that it would be better for people
> to
> > ask the list and run fro
What is the preferred format if writing postgresql documentation?
Is plain text OK?
=
Harry
Join team plico.
http://www.hjackson.org/cgi-bin/folding/index.pl
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
'a,b,c';
>ERROR: schema "a,b,c" does not exist
>
But surely not without the 'TO' word, which is how it appears in
6.13 of the User's Guide?
Regards,
Harry.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
