From: | Jim Mercer <jim(at)reptiles(dot)org> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | purpose/use of pg_start_backup() pg_stop_backup() |
Date: | 2013-04-06 16:46:05 |
Message-ID: | 20130406164605.GV24874@reptiles.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
on the surface, the functions pg_start_backup() and pg_stop_backup() seem to
indicate something very useful.
as i understand it, i could do:
psql -c "pg_start_backup('$(date +%Y%m%d%H%M%S)');"
snapshot/dump $PGDATA
psql -c "pg_stop_backup();"
and this would then create a nice clean snapshot.
however, i'm trying to work out what the restore process is.
its not clear to me if one needs to do anything after restoring the dump.
or, if there is some sort of incremental process that needs to be followed
after the dump.
can someone provide a walk-through of using these functions both for
a backup and a restore?
--
Jim Mercer Reptilian Research jim(at)reptiles(dot)org +1 416 410-5633
"He who dies with the most toys is nonetheless dead"
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2013-04-06 17:38:31 | Re: purpose/use of pg_start_backup() pg_stop_backup() |
Previous Message | Jim Mercer | 2013-04-06 16:40:27 | risks of backup using filesystem snapshot/dump ? |