-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 01:14, filippo wrote:
> On 13 Feb, 14:54, "filippo" <[EMAIL PROTECTED]> wrote:
>
>> 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.
>
filippo wrote:
> On 14 Feb, 08:33, [EMAIL PROTECTED] (Ron Johnson) wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > There's almost definitely a better way to do what you want to do.
> >
> > What benefit are you trying to obtain by creating 720 almost
> > identical databases per month?
>
> I only
On Feb 14, 2:14 am, "filippo" <[EMAIL PROTECTED]> wrote:
> On 13 Feb, 14:54, "filippo" <[EMAIL PROTECTED]> wrote:
>
> > 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.
>
> I could use pg_dump
13 Feb 2007 05:54:44 -0800, filippo <[EMAIL PROTECTED]>:
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 toda
On 14 Feb, 08:33, [EMAIL PROTECTED] (Ron Johnson) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> There's almost definitely a better way to do what you want to do.
>
> What benefit are you trying to obtain by creating 720 almost
> identical databases per month?
I only need the last 24, overwriting e
On 13 Feb, 14:54, "filippo" <[EMAIL PROTECTED]> wrote:
> 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.
I could use pg_dump/pg_restore. pg_dump doesn't have to have exclusive
access to databas
Here is the link to Elein's presentation:
http://www.varlena.com/GeneralBits/Tidbits/tt.pdf
What [about] postgresql "time travel"? I have never used it, and it looks a
little bit unmaintained, but it might be perfect with some tweaking:
---(end of broadcast)--
- Original Message -
From: "Ron Johnson" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, February 14, 2007 3:46 PM
Subject: Re: [GENERAL] backup database by cloning itself
It seems to me that if you really want a historical record of what
certain tables looked like in th
>> Maybe his real goal "all the backups readily available to be read by
>> my program (opening the backup read only)" is to have a historical
>> record of what certain records looked like in the past.
What postgresql "time travel"? I have never used it, and it looks a
little bit unmaintained, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 13:40, Ted Byers wrote:
>> Maybe his real goal "all the backups readily available to be read by
>> my program (opening the backup read only)" is to have a historical
>> record of what certain records looked like in the past.
>>
>> There are
Maybe his real goal "all the backups readily available to be read by
my program (opening the backup read only)" is to have a historical
record of what certain records looked like in the past.
There are other ways of doing that, though.
If your speculation is right, perhaps the OP ought to expl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/07 12:41, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
>> On Tue, 2007-02-13 at 07:54, filippo wrote:
>>> my database is not very big so I want to adopt this backup strategy:
>>> I want to clone my database every 1 hour to anot
Scott Marlowe <[EMAIL PROTECTED]> writes:
> On Tue, 2007-02-13 at 07:54, filippo wrote:
>> 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,
>> overwriti
On Tue, 2007-02-13 at 07:54, filippo wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/07 07:54, filippo wrote:
> 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,
> overw
15 matches
Mail list logo
