Message-ID: <467BBCF2.40506@kostyrka.org>
Date: Fri, 22 Jun 2007 14:13:38 +0200
From: Andreas Kostyrka <andreas@kostyrka.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.10) Gecko/20070329 Thunderbird/1.5.0.10 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Kurt Overberg <kurt@hotdogrecords.com>
Cc: Dan Gorman <dgorman@hi5.com>, Simon Riggs <simon@2ndquadrant.com>,
	Toru SHIMOGAKI <shimogaki.toru@oss.ntt.co.jp>,
	Tom Lane <tgl@sss.pgh.pa.us>, pgsql-performance@postgresql.org
Subject: Re: PITR Backups
References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com>
	<9761.1182472005@sss.pgh.pa.us> <467B3459.9030808@oss.ntt.co.jp>
	<1182509748.9276.178.camel@silverbirch.site>
	<31812EEE-22E7-41CD-B70F-CE861681BABC@hi5.com>
	<1182512289.9276.220.camel@silverbirch.site>
	<69DBDB50-8180-4A53-B753-61C06B2753C1@hi5.com>
	<D11B181D-4E57-450E-B732-FC5FD813E359@hotdogrecords.com>
In-Reply-To: <D11B181D-4E57-450E-B732-FC5FD813E359@hotdogrecords.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

-----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-----