From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Standbys using commas in application_name cannot become sync nodes |
Date: | 2016-02-15 07:33:53 |
Message-ID: | CABUevEzebm80cSJ1PCcJzKss5G1a0J+CMmTm+AjHESko4C6fzA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Feb 15, 2016 at 6:56 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
> On Mon, Feb 15, 2016 at 9:24 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
> > Another possibility to consider would be to mention that in the
> > documentation on back-branches, and simply block its use on HEAD. For
> > the quorum sync patch (which is far from baked yet), we are going to
> > need two extra special characters to identify quorum and priority
> > groups of nodes, so we would need to provide the same solution as for
> > commas.
>
> Horiguchi-san has just mentioned in [1] that one can use double-quotes
> in s_s_names around a node name to bypass the problem. That's
> undocumented though, so wouldn't we want to mention that at least?
> [1]:
> http://www.postgresql.org/message-id/20160215.141102.28792569.horiguchi.kyotaro@lab.ntt.co.jp
>
>
I think that combined with option 4 (comment the possible caveat) is the
best way forward. Especially since we have this ability, there is no need
to restrict it and possibly break existing applications. But documenting it
would clearly be an advantage.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | pravin | 2016-02-15 08:02:40 | BUG #13961: Unexpected behaviour of JSONB_SET if the new_value is null |
Previous Message | Michael Paquier | 2016-02-15 05:56:45 | Re: Standbys using commas in application_name cannot become sync nodes |