[Pgpool-general] Perform maintenance on secondary without stopping pgpool

[louis fridkis]

Lazaro,

Thanks for your response. Are you saying I should re-attach the secondary
and then run PITR? Will this work even if new updates come in via pgpool
while the PITR is running?

Also, can you please provide a link for more information on PITR that is in
English?

Thanks again,

Lou ...



On Tue, Jul 27, 2010 at 5:00 AM, <pgpool-general-request at pgfoundry.org>wrote:

>
> Message: 2
> Date: Mon, 26 Jul 2010 22:04:00 -0400 (CDT)
> From: Lazaro Ruben Garcia Martinez <lgarciam at estudiantes.uci.cu>
> Subject: Re: [Pgpool-general] Perform maintenance on secondary without
>        stopping pgpool
> To: louis fridkis <loufridkis at gmail.com>
> Cc: pgpool-general at pgfoundry.org
> Message-ID:
>        <659179742.45991280196240777.JavaMail.root at ucimail3.uci.cu>
> Content-Type: text/plain; charset="utf-8"
>
> Hello Louis, If you disconnect a node, this node is in detached state, If
> you need to sync the data between the nodes I recommend you a Point in Time
> Recovery, for more information about it you can visit this site.
>
> http://www.postgresql-es.org/node/313
>
> Regards.
>
> ----- "louis fridkis" <loufridkis at gmail.com> escribi?:
> > In our production system, we are running pgpool 2.2.2. We have two
> postgres 8.3.3 instances, each on a different host. We have configured
> pgpool in replication mode. We need to shut down the secondary host so we
> can move it to a different physical location. We do not want to stop the
> application from connecting to pgpool during the time that the secondary is
> down, or afterwords. I have indicated that this is not possible, because, if
> a change is made to the primary postgres DB while the secondary is down,
> then, if we start the secondary and attach it, using pcp_attach_node, the
> two DBs will be out-of-sync. The only way to rectify the out-of-sync
> condition, then, would be to dump the primary and load it into the
> secondary. But, this also would not work, because, if any changes were made,
> to the primary DB, between the time the dump was made and the time it was
> loaded then the two DBs would still be out-of-sync. My question is: am I
> correct? Is there any way to avoid shutting
>  down pgpool in this scenario?
> >
> Lou ...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20100727/1fcdc66e/attachment.html>