Re: Multiple hosts in connection string failed to failover in non-hot standby mode

From: Noah Misch <noah(at)leadboat(dot)com>
To: Hubert Zhang <zhubert(at)vmware(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Multiple hosts in connection string failed to failover in non-hot standby mode
Date: 2020-10-28 10:37:34
Message-ID: 20201028103734.GB3785151@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 27, 2020 at 07:14:14AM +0000, Hubert Zhang wrote:
> Libpq has supported to specify multiple hosts in connection string and enable auto failover when the previous PostgreSQL instance cannot be accessed.
> But when I tried to enable this feature for a non-hot standby, it cannot do the failover with the following messages.
>
> psql: error: could not connect to server: FATAL: the database system is starting up
>
> Document says ' If a connection is established successfully, but authentication fails, the remaining hosts in the list are not tried.'
> I'm wondering is it a feature by design or a bug? If it's a bug, I plan to fix it.

I felt it was a bug, but the community as a whole may or may not agree:
https://postgr.es/m/flat/16508-1a63222835164566%40postgresql.org

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hubert Zhang 2020-10-28 10:41:50 Re: Multiple hosts in connection string failed to failover in non-hot standby mode
Previous Message Julien Rouhaud 2020-10-28 10:15:15 Re: cutting down the TODO list thread