Hi Sandeep. What you were calling Hot Backup is really called Point in
Time Recovery (PITR). Hot Backup means making a complete backup of the
database while it is running, something Postgresql has supported for a
very long time.
On Mon, 7 Oct 2002, Sandeep Chadha wrote:
Hello to all the
I'd have agree on most of what you said. I still think most crashes occur due to data
corruption which can only be recovered by using a good backup.
Anyways my problem is I have a 5 gig database. I run a cron job every hour which runs
pg_dump which takes over 30 minutes to run and degrades
On Wed, 2002-10-09 at 12:46, Sandeep Chadha wrote:
I'd have agree on most of what you said. I still think most crashes occur due to
data corruption which can only be recovered by using a good backup.
Anyways my problem is I have a 5 gig database. I run a cron job every hour which
runs
Rod Taylor wrote:
snip
Oh, if thats your problem then use asynchronous replication instead.
For specific info, the contrib/rserv package does master-slave
asynchronous replication as Rod is suggesting. From memory it was
having troubles working with PostgreSQL 7.2.x, but someone recently
On Wed, 2002-10-09 at 14:04, Justin Clift wrote:
Rod Taylor wrote:
snip
Oh, if thats your problem then use asynchronous replication instead.
For specific info, the contrib/rserv package does master-slave
Thanks. I was having a heck of a time remembering what it was called or
even
