[pgpool-general: 3003] Re: pgpool-general Digest, Vol 33, Issue 3

[Long On]

Hello,

I am also observing node 0 being promoted to master when using
pcp_attach_node, after a recovery of node 0. Node 1 is master and should
remain so but I see a failback sequence happening in pgpool.log. After
which write statements are no longer possible since pgpool is sending them
to node 0, which is now standby.

Is there an option in pcp_attach_node to specify if promotion should happen
or not?

I am using pgpool from ubuntu 14.04 distro, which is 3.3.2 I think.

Long



Date: Tue, 1 Jul 2014 12:48:31 -0700
> From: Santosh Mathew <santosh.checkmail at gmail.com>
> To: pgpool-general at pgpool.net
> Subject: [pgpool-general: 3000] Can backend0 be a slave ?
> Message-ID:
>         <CA+Q=
> xBjjdUEhQ89JvYv96znPTAPv5Y1NiunA4UsTT-EZQ8mvxw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I have 3 postgres nodes in streaming replication mode with two pgpools in
> active -stanby configuration.
>
> Is my observation right that pgpool always looks at backend0 as the master
> ? Supposing there is a failure in backend0 and backend1 is promoted as the
> new master. In this case if we are able to fix backend0 and attach it back
> as the slave of the new master (backend1), pgpool still assumes that
> backend0 is the master and tries to write to it. Is there a configuration
> setting to tell pgpool that backend0 is a slave and backend1 is a master ?
>
> Thanks in advance for your help.
>
> - Santosh
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140701/ec0ab742/attachment.html
> >
>
> ------------------------------
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140702/138eebde/attachment.html>