Re: backup database by cloning itself - Mailing list pgsql-general

From Filip Rembiałkowski
Subject Re: backup database by cloning itself
Date
Msg-id 92869e660702140141l852c7aakb622c2de36f9da08@mail.gmail.com
Whole thread Raw
In response to backup database by cloning itself  ("filippo" <filippo2991@virgilio.it>)
List pgsql-general
13 Feb 2007 05:54:44 -0800, filippo <filippo2991@virgilio.it>:
> Hello,
>
> my database is not very big so I want to adopt this backup strategy:
>
> I want to clone my database every 1 hour  to another
> database 'currenttime_mydatabase' in order to have 24 backup a day,
> overwriting the yesterday backups by today-same-time backups.
>
> This is good for me because I have all the backups readily available
> to be read by my program (opening the backup read only). This is a
> very important for my needs.
>
> I'm writing a script run by cron each hour to do accomplish the backup
> task.
>
> My target is to have the backup operation not affecting the users, so
> I want to be able to copy a database even if the database is used by
> someone.
>
> Can I use
> CREATE DATABASE my_backup_database TEMPLATE current_database?

no. database used as template must not be accessed during copy

>
>  Is there a better way to get what I need?

you can script this:

pg_dump sourcedb |  psql targetdb


--
Filip Rembiałkowski

pgsql-general by date:

Previous
From: "ksherlock@gmail.com"
Date:
Subject: Re: Stored Procedure examples
Next
From: Alexander Elgert
Date:
Subject: massive memory allocation until machine crashes