Skip site navigation (1) Skip section navigation (2)

Re: PITR Backups

From: Andreas Kostyrka <andreas(at)kostyrka(dot)org>
To: Kurt Overberg <kurt(at)hotdogrecords(dot)com>
Cc: Dan Gorman <dgorman(at)hi5(dot)com>,Simon Riggs <simon(at)2ndquadrant(dot)com>,Toru SHIMOGAKI <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: PITR Backups
Date: 2007-06-22 12:13:38
Message-ID: 467BBCF2.40506@kostyrka.org (view raw or flat)
Thread:
Lists: pgsql-performance
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wasn't it select pg_start_backup('backuplabel');?

Andreas

Kurt Overberg wrote:
> You can use the psql command line to run:
> 
> "select pg_start_backup();"
> 
> ...then when you're done,
> 
> "select pg_stop_backup();"
> 
> if you want an example from the unix command line:
> 
> psql -c "select pg_start_backup();" database_name
> 
> then
> 
> psql -c "select pg_stop_backup();" database_name
> 
> /kurt
> 
> 
> On Jun 22, 2007, at 7:51 AM, Dan Gorman wrote:
> 
>> Ah okay. I understand now. So how can I signal postgres I'm about to
>> take a backup ? (read doc from previous email ? )
>>
>> Regards,
>> Dan Gorman
>>
>> On Jun 22, 2007, at 4:38 AM, Simon Riggs wrote:
>>
>>> On Fri, 2007-06-22 at 04:10 -0700, Dan Gorman wrote:
>>>> This snapshot is done at the LUN (filer) level, postgres is un-aware
>>>> we're creating a backup, so I'm not sure how pg_start_backup() plays
>>>> into this ...
>>>
>>> Postgres *is* completely unaware that you intend to take a backup, that
>>> is *exactly* why you must tell the server you intend to make a backup,
>>> using pg_start_backup() and pg_stop_backup(). That way Postgres will
>>> flush its buffers, so that they are present on storage when you make the
>>> backup.
>>>
>>> Is the procedure for Oracle or any other transactional RDBMS any
>>> different?
>>>
>>> --  Simon Riggs
>>>   EnterpriseDB   http://www.enterprisedb.com
>>>
>>>
>>>
>>> ---------------------------(end of broadcast)---------------------------
>>> TIP 9: In versions below 8.0, the planner will ignore your desire to
>>>        choose an index scan if your joining column's datatypes do not
>>>        match
>>
>>
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 3: Have you checked our extensive FAQ?
>>
>>               http://www.postgresql.org/docs/faq
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGe7zyHJdudm4KnO0RAgyaAJ9Vz52izICKYkep/wZpJMFPkfAiuQCfZcjB
yUYM6rYu18HmTAs3F4VaGJo=
=n3vX
-----END PGP SIGNATURE-----

In response to

pgsql-performance by date

Next:From: Simon RiggsDate: 2007-06-22 12:14:46
Subject: Re: PITR Backups
Previous:From: Kurt OverbergDate: 2007-06-22 12:10:46
Subject: Re: PITR Backups

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group