From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | lejeczek <peljasz(at)yahoo(dot)co(dot)uk> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Replication & TLS encryption - how? |
Date: | 2021-04-08 02:59:07 |
Message-ID: | d7c701fd45117f1281f7342be412c5297610755f.camel@cybertec.at |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, 2021-04-07 at 21:12 +0100, lejeczek wrote:
> On 07/04/2021 17:36, Tom Lane wrote:
> > lejeczek <peljasz(at)yahoo(dot)co(dot)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.
Then include "sslcert" in "primary_conninfo".
You can use all the libpq connection parameters:
https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | lejeczek | 2021-04-08 08:21:30 | Re: Replication & TLS encryption - how? |
Previous Message | lejeczek | 2021-04-07 20:12:15 | Re: Replication & TLS encryption - how? |