From: | Benjamin Smith <lists(at)benjamindsmith(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgsql 9.0.1 table corruption |
Date: | 2011-04-16 00:56:07 |
Message-ID: | 201104151756.07766.lists@benjamindsmith.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday, April 15, 2011 09:50:57 AM Tom Lane wrote:
> If you simply unpacked the tar archive and started a postmaster on that,
> you'd be pretty much guaranteed to get a corrupt database. The tar
> archive is not a valid snapshot by itself --- you have to replay
> whatever WAL was generated during the archiving sequence in order to get
> to a consistent database state.
I have, more than once, "moved" a PG instance from one machine to another with
the following sequence, without apparent issue. is there anything I'm missing
and/or need to be concerned with?
1) service postgresql stop;
2) rsync -vaz /var/lib/pgsql root(at)newserver:/var/lib/pgsql;
3) ssh root(at)newserver;
4) (edit postgresql.conf, set IP addresses, memory, etc)
5) service postgresql start;
This is a "done at 10 PM on Friday night" kind of process.
-Ben
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-16 01:27:51 | Re: pgsql 9.0.1 table corruption |
Previous Message | Rob Sargent | 2011-04-15 23:42:00 | Re: Can a nested function determine it is being called within a trigger? |