PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID16508
PG Version10.11
OSrhel7
Opened2020-06-24 08:17:44+00
Reported byCyril Jouve
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      16508
Logged by:          Cyril Jouve
Email address:      (redacted)
PostgreSQL version: 10.11
Operating system:   rhel7
Description:        

Hello,

I'm connection to pg10 using psql (tried with clients psql 10.11 & psql
12.2) using a connection string such as:
psql 'dbname=xxxxx1,xxxxx2,xxxxx3,xxxxx4 target_session_attrs=read-write'

the connection to first database (xxxxx1) fail with the error:
psql.bin: FATAL:  the database system is starting up

which is correct according to postgres state on that machine,
but then I would expect the psql tries the next server (xxxxx2) with is in
the one acceptiong the connection params (target_session_attrs=read-write)

instead of the error.

If I swap the connection parameters like this: psql
'dbname=xxxxx2,xxxxx1,xxxxx3,xxxxx4 target_session_attrs=read-write'
(swapped xxxx1/xxxx2), psql is able to connect to xxxxx2.

Messages

DateAuthorSubject
2020-06-24 08:17:44+00PG Bug reporting formBUG #16508: using multi-host connection string when the first host is starting fails
2020-08-13 07:55:39+00Noah MischRe: BUG #16508: using multi-host connection string when the first host is starting fails