Re: [Bug fix]If recovery.conf has target_session_attrs=read-write, the standby fails to start.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: "Higuchi, Daisuke" <higuchi(dot)daisuke(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [Bug fix]If recovery.conf has target_session_attrs=read-write, the standby fails to start.
Date: 2017-05-19 19:58:53
Message-ID: CA+TgmoYeQp+y6511uT1SyE3kHdKY0VsfZZfEFZo0ozUqQg7ThA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 19, 2017 at 12:51 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Fri, May 19, 2017 at 1:16 PM, Higuchi, Daisuke
> <higuchi(dot)daisuke(at)jp(dot)fujitsu(dot)com> wrote:
>> The reason of this problem is that sending 'show transaction_read_only' is failed.
>> 'show' must be in uppercase letters because the streaming replication protocol only accepts capital letters.
>> In psql and libpq applications that do not use the streaming replication protocol, this error does not occur.
>>
>> The attached patch fixes this. This patch changes 'show transaction_read_only' to 'SHOW transaction_read_only'.
>
> if (!PQsendQuery(conn,
> - "show transaction_read_only"))
> + "SHOW transaction_read_only"))
> Or perhaps the replication command parser could be made more flexible
> with lower-case characters for replication commands?

Maybe, but that sounds a lot more likely to inflict collateral damage
of some kind than the originally-proposed fix, so I've committed that
fix instead.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-05-19 20:01:36 Re: Preliminary results for proposed new pgindent implementation
Previous Message Tom Lane 2017-05-19 19:53:35 Precision and rounding fixes for money type