[pgpool-general: 4602] Re: Two masters

[James Sewell]

Hey,

OK, this makes sense.

It would still be nice to have an option, as when third party clustering
solutions are used two masters would still be a possibility (although
pretty unlikely).

Cheers,



James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________


Level 2, 50 Queen St, Melbourne VIC 3000

*P *(+61) 3 8370 8000  *W* www.lisasoft.com  *F *(+61) 3 8370 8099


On Thu, Mar 31, 2016 at 9:53 AM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> Actually the mistakenly promoted primary is getting too behind from
> the true primary, pgpool will not load balance to the the mistakenly
> promoted primary.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
> > It would be nice if there was an option to stop load balancing if two
> were
> > found (regardless of any rules or who is newer).
> >
> > That would be the safest option I think?
> >
> > Cheers,
> > James Sewell
> >
> > On Wednesday, 30 March 2016, Tatsuo Ishii <ishii at postgresql.org> wrote:
> >
> >> Currently there is no reliable way to detect duplicated primary nodes.
> >> However in practice you can notice that replication delay is getting
> >> larger with the mistakenly promoted primary because no data
> >> propagation from the real primary is made to the primary.
> >>
> >> Best regards,
> >> --
> >> Tatsuo Ishii
> >> SRA OSS, Inc. Japan
> >> English: http://www.sraoss.co.jp/index_en.php
> >> Japanese:http://www.sraoss.co.jp
> >>
> >> > Hello,
> >> >
> >> > If PGPool detects two masters when in steaming replication mode (which
> >> > could have been caused by operator error, another HA product or
> whatever)
> >> > is there a way to make it disallow connections?
> >> >
> >> > Essentially I want to ensure that there is never two servers which
> >> respond
> >> > false to pg_is_in_replication at once (as that would be bad).
> >> >
> >> > Bonus points if I could select the current master as the one with the
> >> > highest timeline!
> >> >
> >> > Cheers,
> >> >
> >> >
> >> > James Sewell,
> >> > PostgreSQL Team Lead / Solutions Architect
> >> > ______________________________________
> >> >
> >> >
> >> > Level 2, 50 Queen St, Melbourne VIC 3000
> >> >
> >> > *P *(+61) 3 8370 8000  *W* www.lisasoft.com  *F *(+61) 3 8370 8099
> >> >
> >> > --
> >> >
> >> >
> >> > ------------------------------
> >> > The contents of this email are confidential and may be subject to
> legal
> >> or
> >> > professional privilege and copyright. No representation is made that
> this
> >> > email is free of viruses or other defects. If you have received this
> >> > communication in error, you may not copy or distribute any part of it
> or
> >> > otherwise disclose its contents to anyone. Please advise the sender of
> >> your
> >> > incorrect receipt of this correspondence.
> >>
> >
> >
> > --
> >
> > James Sewell,
> > PostgreSQL Team Lead / Solutions Architect
> > ______________________________________
> >
> >
> > Level 2, 50 Queen St, Melbourne VIC 3000
> >
> > *P *(+61) 3 8370 8000  *W* www.lisasoft.com  *F *(+61) 3 8370 8099
> >
> > --
> >
> >
> > ------------------------------
> > The contents of this email are confidential and may be subject to legal
> or
> > professional privilege and copyright. No representation is made that this
> > email is free of viruses or other defects. If you have received this
> > communication in error, you may not copy or distribute any part of it or
> > otherwise disclose its contents to anyone. Please advise the sender of
> your
> > incorrect receipt of this correspondence.
>

-- 


------------------------------
The contents of this email are confidential and may be subject to legal or 
professional privilege and copyright. No representation is made that this 
email is free of viruses or other defects. If you have received this 
communication in error, you may not copy or distribute any part of it or 
otherwise disclose its contents to anyone. Please advise the sender of your 
incorrect receipt of this correspondence.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160331/c35e1538/attachment.html>