Re: Standbys using commas in application_name cannot become sync nodes

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: 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 05:56:45
Message-ID: CAB7nPqT8xxt3D9Zq8xy-ziQXJFAwGnihPiyTz=hOy=91PUAQFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2016-02-15 07:33:53 Re: Standbys using commas in application_name cannot become sync nodes
Previous Message Tom Lane 2016-02-15 01:09:13 Re: BUG #13960: plpython fails with certain function names