From: | Mark <admin(at)asarian-host(dot)net> |
---|---|
To: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | 'Hot' backup of PostgreSQL dbases |
Date: | 2009-05-14 11:13:17 |
Message-ID: | 200905141113.n4EBDGBN033779@asarian-host.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Using PostgreSQL 8.3.7, I'd like to make a 'hot' backup of my dbases.
I've been using "pg_dumpall -c -o" for a while, but I realize that this is
no good. After all, for a restore, the PostgreSQL server needs to be up!
And what happens if the dbases crash/become corrupted (say, after a
power-outage), and PostgreSQL won't start up any more? In MySQL, this was
easy. In a Perl script I did something like: "FLUSH TABLES WITH READ
LOCK", and then I proceeded to tar the entire dbases directory (so I could
untar, without the MySQL server needing to be up).
Can something similiar be done in PostgreSQL, *without* bringing down the
server in its entirety?
Thanks,
- Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Ognjen Blagojevic | 2009-05-14 18:28:01 | Unexpected behaviour of ORDER BY and LIMIT/OFFSET |
Previous Message | Ilya Urikh | 2009-05-14 06:56:54 | Re: C-Language function invocation from another one. |