| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Steve Crawford <scrawford(at)pinpointresearch(dot)com>, Timmy Siu <timmy(dot)siu(at)aol(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: TCP Wrappers |
| Date: | 2019-10-09 23:29:08 |
| Message-ID: | CAMsr+YHtFL_OBALJOFPqfKiTDcxYjOGna4KL5Y7zuA91cZXNZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 10 Oct 2019 at 07:15, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> That doesn't bode well for the number of people who would use or care
> about such a feature.
>
Agreed. tcp_wrappers predates the widespread availability of easy,
effective software firewalls. Back when services listened on 0.0.0.0 and if
you were lucky you had ipfwadm, tcp_wrappers made a lot of sense. Now it's
IMO a pointless layer of additional complexity that no longer serves a
purpose.
--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-10-09 23:41:54 | Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |
| Previous Message | Tomas Vondra | 2019-10-09 23:28:36 | Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |