pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedCascading Recovery
7+ messages / 4 participants
[nested] [flat]
* Cascading Recovery
@ 2011-02-11 04:43 Selva manickaraja <mavles78@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Selva manickaraja @ 2011-02-11 04:43 UTC (permalink / raw)
To: pgsql-admin
We are considering on using a primary and 2 secondary machines. But our plan
is to cascade the recovery as follows:
1. Primary Machine-A (read and write operation)
2. Secondary Machine-B (recover from Machine A)
3. Secondary Machine-C (recover from Machine B)
We are planning this kind of recovery as we want to phase out recovery
interval between C and B 30 minutes.
Can this be achieved by PostgreSQL.
Thank you.
Warmest Regards,
Selvam
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Cascading Recovery
@ 2011-02-11 07:35 Guillaume Lelarge <guillaume@lelarge.info>
parent: Selva manickaraja <mavles78@gmail.com>
0 siblings, 2 replies; 7+ messages in thread
From: Guillaume Lelarge @ 2011-02-11 07:35 UTC (permalink / raw)
To: Selva manickaraja <mavles78@gmail.com>; +Cc: pgsql-admin
Le 11/02/2011 05:43, Selva manickaraja a écrit :
> We are considering on using a primary and 2 secondary machines. But our plan
> is to cascade the recovery as follows:
>
> 1. Primary Machine-A (read and write operation)
> 2. Secondary Machine-B (recover from Machine A)
> 3. Secondary Machine-C (recover from Machine B)
>
> We are planning this kind of recovery as we want to phase out recovery
> interval between C and B 30 minutes.
>
> Can this be achieved by PostgreSQL.
>
Not with Streaming Replication. But you can achieve this with a
different replication engine, like Slony.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Cascading Recovery
@ 2011-02-11 08:17 Ashish Nauriyal <ashish.nauriyal@enterprisedb.com>
parent: Guillaume Lelarge <guillaume@lelarge.info>
1 sibling, 0 replies; 7+ messages in thread
From: Ashish Nauriyal @ 2011-02-11 08:17 UTC (permalink / raw)
To: Guillaume Lelarge <guillaume@lelarge.info>; +Cc: Selva manickaraja <mavles78@gmail.com>; pgsql-admin
Can be achieved using Slony and called cascaded subscription of sets.
Ashish,
EnterpriseDB Corp.
The Enterprise PostgreSQL Company
On Fri, Feb 11, 2011 at 1:05 PM, Guillaume Lelarge
<guillaume@lelarge.info>wrote:
> Le 11/02/2011 05:43, Selva manickaraja a écrit :
> > We are considering on using a primary and 2 secondary machines. But our
> plan
> > is to cascade the recovery as follows:
> >
> > 1. Primary Machine-A (read and write operation)
> > 2. Secondary Machine-B (recover from Machine A)
> > 3. Secondary Machine-C (recover from Machine B)
> >
> > We are planning this kind of recovery as we want to phase out recovery
> > interval between C and B 30 minutes.
> >
> > Can this be achieved by PostgreSQL.
> >
>
> Not with Streaming Replication. But you can achieve this with a
> different replication engine, like Slony.
>
>
> --
> Guillaume
> http://www.postgresql.fr
> http://dalibo.com
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Cascading Recovery
@ 2011-02-11 17:43 Selva manickaraja <mavles78@gmail.com>
parent: Guillaume Lelarge <guillaume@lelarge.info>
1 sibling, 1 reply; 7+ messages in thread
From: Selva manickaraja @ 2011-02-11 17:43 UTC (permalink / raw)
To: Guillaume Lelarge <guillaume@lelarge.info>; +Cc: pgsql-admin
If not with Streaming Replication, what about Continous Archiving Mode?
On Fri, Feb 11, 2011 at 3:35 PM, Guillaume Lelarge
<guillaume@lelarge.info>wrote:
> Le 11/02/2011 05:43, Selva manickaraja a écrit :
> > We are considering on using a primary and 2 secondary machines. But our
> plan
> > is to cascade the recovery as follows:
> >
> > 1. Primary Machine-A (read and write operation)
> > 2. Secondary Machine-B (recover from Machine A)
> > 3. Secondary Machine-C (recover from Machine B)
> >
> > We are planning this kind of recovery as we want to phase out recovery
> > interval between C and B 30 minutes.
> >
> > Can this be achieved by PostgreSQL.
> >
>
> Not with Streaming Replication. But you can achieve this with a
> different replication engine, like Slony.
>
>
> --
> Guillaume
> http://www.postgresql.fr
> http://dalibo.com
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Fwd: Cascading Recovery
@ 2011-02-13 15:35 Selva manickaraja <mavles78@gmail.com>
parent: Selva manickaraja <mavles78@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Selva manickaraja @ 2011-02-13 15:35 UTC (permalink / raw)
To: pgsql-admin
Any updates?
---------- Forwarded message ----------
From: Selva manickaraja <mavles78@gmail.com>
Date: Sat, Feb 12, 2011 at 1:43 AM
Subject: Re: [ADMIN] Cascading Recovery
To: Guillaume Lelarge <guillaume@lelarge.info>
Cc: pgsql-admin@postgresql.org
If not with Streaming Replication, what about Continous Archiving Mode?
On Fri, Feb 11, 2011 at 3:35 PM, Guillaume Lelarge
<guillaume@lelarge.info>wrote:
> Le 11/02/2011 05:43, Selva manickaraja a écrit :
> > We are considering on using a primary and 2 secondary machines. But our
> plan
> > is to cascade the recovery as follows:
> >
> > 1. Primary Machine-A (read and write operation)
> > 2. Secondary Machine-B (recover from Machine A)
> > 3. Secondary Machine-C (recover from Machine B)
> >
> > We are planning this kind of recovery as we want to phase out recovery
> > interval between C and B 30 minutes.
> >
> > Can this be achieved by PostgreSQL.
> >
>
> Not with Streaming Replication. But you can achieve this with a
> different replication engine, like Slony.
>
>
> --
> Guillaume
> http://www.postgresql.fr
> http://dalibo.com
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Cascading Recovery
@ 2011-02-13 21:53 Scott Mead <scottm@openscg.com>
parent: Selva manickaraja <mavles78@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Scott Mead @ 2011-02-13 21:53 UTC (permalink / raw)
To: Selva manickaraja <mavles78@gmail.com>; +Cc: pgsql-admin
On Sun, Feb 13, 2011 at 10:35 AM, Selva manickaraja <mavles78@gmail.com>wrote:
> Any updates?
You can't use any wal based replication like that. When a node is in
recovery mode, it doesn't log.
--Scottie
>
>
> ---------- Forwarded message ----------
> From: Selva manickaraja <mavles78@gmail.com>
> Date: Sat, Feb 12, 2011 at 1:43 AM
> Subject: Re: [ADMIN] Cascading Recovery
> To: Guillaume Lelarge <guillaume@lelarge.info>
> Cc: pgsql-admin@postgresql.org
>
>
> If not with Streaming Replication, what about Continous Archiving Mode?
>
>
> On Fri, Feb 11, 2011 at 3:35 PM, Guillaume Lelarge <guillaume@lelarge.info
> > wrote:
>
>> Le 11/02/2011 05:43, Selva manickaraja a écrit :
>> > We are considering on using a primary and 2 secondary machines. But our
>> plan
>> > is to cascade the recovery as follows:
>> >
>> > 1. Primary Machine-A (read and write operation)
>> > 2. Secondary Machine-B (recover from Machine A)
>> > 3. Secondary Machine-C (recover from Machine B)
>> >
>> > We are planning this kind of recovery as we want to phase out recovery
>> > interval between C and B 30 minutes.
>> >
>> > Can this be achieved by PostgreSQL.
>> >
>>
>> Not with Streaming Replication. But you can achieve this with a
>> different replication engine, like Slony.
>>
>>
>> --
>> Guillaume
>> http://www.postgresql.fr
>> http://dalibo.com
>>
>
>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Cascading Recovery
@ 2011-02-14 02:54 Selva manickaraja <mavles78@gmail.com>
parent: Scott Mead <scottm@openscg.com>
0 siblings, 0 replies; 7+ messages in thread
From: Selva manickaraja @ 2011-02-14 02:54 UTC (permalink / raw)
To: Scott Mead <scottm@openscg.com>; +Cc: pgsql-admin
Thank you for the info.
On Mon, Feb 14, 2011 at 5:53 AM, Scott Mead <scottm@openscg.com> wrote:
>
>
> On Sun, Feb 13, 2011 at 10:35 AM, Selva manickaraja <mavles78@gmail.com>wrote:
>
>> Any updates?
>
>
> You can't use any wal based replication like that. When a node is in
> recovery mode, it doesn't log.
>
> --Scottie
>
>
>>
>>
>> ---------- Forwarded message ----------
>> From: Selva manickaraja <mavles78@gmail.com>
>> Date: Sat, Feb 12, 2011 at 1:43 AM
>> Subject: Re: [ADMIN] Cascading Recovery
>> To: Guillaume Lelarge <guillaume@lelarge.info>
>> Cc: pgsql-admin@postgresql.org
>>
>>
>> If not with Streaming Replication, what about Continous Archiving Mode?
>>
>>
>> On Fri, Feb 11, 2011 at 3:35 PM, Guillaume Lelarge <
>> guillaume@lelarge.info> wrote:
>>
>>> Le 11/02/2011 05:43, Selva manickaraja a écrit :
>>> > We are considering on using a primary and 2 secondary machines. But our
>>> plan
>>> > is to cascade the recovery as follows:
>>> >
>>> > 1. Primary Machine-A (read and write operation)
>>> > 2. Secondary Machine-B (recover from Machine A)
>>> > 3. Secondary Machine-C (recover from Machine B)
>>> >
>>> > We are planning this kind of recovery as we want to phase out recovery
>>> > interval between C and B 30 minutes.
>>> >
>>> > Can this be achieved by PostgreSQL.
>>> >
>>>
>>> Not with Streaming Replication. But you can achieve this with a
>>> different replication engine, like Slony.
>>>
>>>
>>> --
>>> Guillaume
>>> http://www.postgresql.fr
>>> http://dalibo.com
>>>
>>
>>
>>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2011-02-14 02:54 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-02-11 04:43 Cascading Recovery Selva manickaraja <mavles78@gmail.com>
2011-02-11 07:35 ` Guillaume Lelarge <guillaume@lelarge.info>
2011-02-11 08:17 ` Ashish Nauriyal <ashish.nauriyal@enterprisedb.com>
2011-02-11 17:43 ` Selva manickaraja <mavles78@gmail.com>
2011-02-13 15:35 ` Selva manickaraja <mavles78@gmail.com>
2011-02-13 21:53 ` Scott Mead <scottm@openscg.com>
2011-02-14 02:54 ` Selva manickaraja <mavles78@gmail.com>
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