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

Re: PITR Backups

From: Dan Gorman <dgorman(at)hi5(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: "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 11:51:19
Message-ID: 69DBDB50-8180-4A53-B753-61C06B2753C1@hi5.com (view raw or flat)
Thread:
Lists: pgsql-performance
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



In response to

Responses

pgsql-performance by date

Next:From: Adam Tauno WilliamsDate: 2007-06-22 12:05:46
Subject: Re: PostgreSQL Configuration Tool for Dummies
Previous:From: Simon RiggsDate: 2007-06-22 11:38:09
Subject: Re: PITR Backups

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