From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | jv(dot)cyril(at)gmail(dot)com |
Subject: | BUG #16508: using multi-host connection string when the first host is starting fails |
Date: | 2020-06-24 08:17:44 |
Message-ID: | 16508-1a63222835164566@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16508
Logged by: Cyril Jouve
Email address: jv(dot)cyril(at)gmail(dot)com
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-06-25 06:45:41 | Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data |
Previous Message | Michael Paquier | 2020-06-24 07:59:21 | Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data |