From: lejeczek <peljasz@yahoo.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Replication & TLS encryption - how?
Date: Wed, 7 Apr 2021 21:12:15 +0100
Message-ID: <7e89a9be-e788-23fc-6b1b-2ee67586d452@yahoo.co.uk> (raw)
In-Reply-To: <1596782.1617813374@sss.pgh.pa.us>
References: <54a5bf2b-0504-02c0-e5a2-ab24173abcdb.ref@yahoo.co.uk>
<54a5bf2b-0504-02c0-e5a2-ab24173abcdb@yahoo.co.uk>
<1596782.1617813374@sss.pgh.pa.us>
On 07/04/2021 17:36, Tom Lane wrote:
> lejeczek <peljasz@yahoo.co.uk> writes:
>> A novice here thus please go easy on me as I ask this - I
>> see docs/howtos all over the place be those either talk of
>> encryption or replication. I failed to find one which blend
>> these two concepts together - sure it's possible to pgSQL
>> replication encrypted, right?
> Replication connections work exactly like normal sessions for
> this purpose. Just make sure you set any required parameters
> in the standby's connection string.
>
> regards, tom lane
>
>
Thanks. Would you know how '|clientcert=1' fits into the
equation?
With it present in pg_hba.conf pgSQL was not happy saying:
FATAL: connection requires a valid client certificate.
|
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peljasz@yahoo.co.uk
Subject: Re: Replication & TLS encryption - how?
In-Reply-To: <7e89a9be-e788-23fc-6b1b-2ee67586d452@yahoo.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox