From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PG equivalent of "mysqlhotcopy"? |
Date: | 2009-07-31 17:30:20 |
Message-ID: | 418D70F0-298A-47B4-B991-6FB236D877B6@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
Le 30 juil. 09 à 15:34, Phoenix Kiula a écrit :
> I know about pg_dumpall, which creates a humongous SQL file, but is
> there something equivalent in the postgresql world, like a
> "pgsqlhotcopy" which copies data folders in a similar way as
> mysqlhotcopy?
Copying the raw data files of a live database only works under certain
conditions with PostgreSQL, in short you have to tell it about what
you're going to do for it to cooperate. That's pg_start_backup()
function and friends.
Now, the generic technique provided by PostgreSQL is called PITR,
Point In Time Recovery. You'll find ready to go software to drive
this, in order of personal preference :
- walmgr from Skytools
http://wiki.postgresql.org/wiki/Skytools#walmgr
http://skytools.projects.postgresql.org/doc/walmgr.html
https://developer.skype.com/SkypeGarage/DbProjects/SkyTools/WalMgr
- pitrtools
http://projects.commandprompt.com/public/pitrtools/
- pg_standby (read carefully the 8.3 era behavior of this one)
it's in the contribs
Those 3 solutions are packaged in debian and maybe some other
distributions or OS.
Regards,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2009-07-31 17:45:58 | Re: Limiting records in pg_dump |
Previous Message | Oliver Kohll - Mailing Lists | 2009-07-31 17:27:41 | Division by zero |