Re: Let people set host(no)ssl settings from initdb

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Fetter <david(at)fetter(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Cary Huang <cary(dot)huang(at)highgo(dot)ca>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Let people set host(no)ssl settings from initdb
Date: 2021-03-03 14:07:30
Message-ID: c3c67e49-52b4-7f86-6132-7e5901fe7239@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01.01.21 14:12, Magnus Hagander wrote:
> That said, I agree with not adding it as an option to initdb. You'll
> quickly get to the point where you specify the whole pg_hba file on the
> commandline to initdb -- and most people today who actually care that
> much about it would have their pg_hba.conf file under some sort of
> configuration management anyway, whether it's ansible, chef, puppet or
> something else.

I think there is enough sustained opposition to this patch that we can
mark this as rejected in the commitfest.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruno Lavoie 2021-03-03 14:13:43 Re: PROXY protocol support
Previous Message Dilip Kumar 2021-03-03 14:07:21 Re: Parallel INSERT (INTO ... SELECT ...)