Postgres Pro
Downloads
Home   >   mailing lists

Re: Libpq support to connect to standby server as priority - Mailing list pgsql-hackers

From Haribabu Kommi
Subject Re: Libpq support to connect to standby server as priority
Date
Msg-id CAJrrPGeM4NzFOjiLKmcQ+wAN=CAJDdUw3ar2m_Q4EZsZYrUdRw@mail.gmail.com
Whole thread Raw
In response to Re: Libpq support to connect to standby server as priority  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses RE: Libpq support to connect to standby server as priority
List pgsql-hackers
Tree view

On Wed, Mar 27, 2019 at 5:17 PM Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com> wrote:
I've looked through 0004-0007.  I've only found the following:

(5) 0005
With this read-only option type, application can connect to
connecting to a read-only server in the list of hosts, in case
if there is any read-only servers available, the connection
attempt fails.

"connecting to" can be removed.

in case if there is any read-only servers
-> If There's no read only server

Thanks for the review.

I corrected all the comments that are raised by you and attached updated version of patches
along with implementation of WIP in_recovery GUC_REPORT variable. This patch has used some
of the implementations that are provided earlier in thread [1].

During the implementation of in_recovery configuration variable, I see a lot of code addition just
for this variable, is this worth it?


Regards,
Haribabu Kommi
Fujitsu Australia
Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonpath
Next
From: "Fred .Flintstone"
Date:
Subject: Re: PostgreSQL pollutes the file system