pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Naomi Walker <nwalke@eldocomp.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: PITR recovery
Date: Tue, 9 Jan 2007 10:49:31 -0700
Message-ID: <45A3D5AB.6000403@eldocomp.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0701090747120.17741@coe.tamu.edu>
References: <Pine.GSO.4.64.0701051218340.1164@coe.tamu.edu>
	<20070105201610.GB20611@wolff.to>
	<Pine.GSO.4.64.0701090747120.17741@coe.tamu.edu>

Speaking of PITR, it would be great if I could perform a PITR for a
particular database in an instance.
My options otherwise would be to install the instance elsewhere and
extract, or, create an instance for
each database (not reasonable, since we have dozens)....

We backup each database separately each even with a pg_dump.  Is there a
way to segregate WAL's?

Naomi



Ben K. wrote:
> On Fri, 5 Jan 2007, Bruno Wolff III wrote:
>
>>> I.e. would it be possible to restore the file system backup
>>> and use the PITR method from a Solaris/SPARC main to a Linux backup,
>>> using
>>> their respective native file system? What are the minimal conditions
>>> to be
>>> met?
>>
>> No the data is not only dependent on the platform, but also on the
>> configure
>> options used for the build.
>
>
---------------------------------------------------------------------------- 
Naomi Walker                          Chief Information Officer 
Mphasis Healthcare Solutions          nwalker@mhs.mphasis.com 
  ---An EDS Company                   602-604-3100 
---------------------------------------------------------------------------- 
A positive attitude may not solve all your problems, but it will annoy 
enough people to make it worth the effort. --Herm Albright (1876 - 1944)
----------------------------------------------------------------------------

-- CONFIDENTIALITY NOTICE --

Information transmitted by thisĀ e-mail is proprietary to MphasiS and/or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that isĀ privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this e-mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at mailmaster@mphasis.com and delete this mail from your records.



view thread (10+ messages)

Message-ID: <45A3D5AB.6000403@eldocomp.com>
Permalink:  ../45A3D5AB.6000403@eldocomp.com/
Also on:    postgresql.org/message-id/45A3D5AB.6000403@eldocomp.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: nwalke@eldocomp.com
  Subject: Re: PITR recovery
  In-Reply-To: <45A3D5AB.6000403@eldocomp.com>
  References: <Pine.GSO.4.64.0701051218340.1164@coe.tamu.edu> <20070105201610.GB20611@wolff.to> <Pine.GSO.4.64.0701090747120.17741@coe.tamu.edu> <45A3D5AB.6000403@eldocomp.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox