Content-Type: multipart/alternative;
 boundary=Apple-Mail-5CCA9BF3-0C21-481B-81BE-658C4C65CC5E
Content-Transfer-Encoding: 7bit
From: Peter Vandivier <petervandivier@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: BUG #16695: pg_hba_file_rules NULL address and netmask
Date: Mon, 2 Nov 2020 22:26:25 +0000
Message-Id: <258C6CBF-BF3B-4042-B1E2-EC67634C17A0@gmail.com>
References: <826464.1604355302@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
In-Reply-To: <826464.1604355302@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk


--Apple-Mail-5CCA9BF3-0C21-481B-81BE-658C4C65CC5E
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Apologies - please find screencaps and context at the following

- https://postgresteam.slack.com/archives/C0FS3UTAP/p1603440839348800
- https://topanswers.xyz/transcript?room=3D2&id=3D78663&year=3D2020&month=3D=
10#c78663

By way of description - IP address/netmask pairs given in pg_hba.conf are no=
t read into the system view pg_hba_file_rules even in well formed and defaul=
t installations. The shell commands given in the initial email are meant to g=
ive a minimum reproduction of this behavior when executed on FreeBSD 11

A default install on RHEL querying pg_hba_file_rules would show correspondin=
g non-null values as appropriate

Kind regards

Peter Vandivier
Sent from my iPhone
Please excuse typos and brevity

On Nov 2, 2020, at 22:15, Tom Lane <tgl@sss.pgh.pa.us> wrote:

=EF=BB=BFPG Bug reporting form <noreply@postgresql.org> writes:
> pg_hba_file_rules reports NULL address and netmask values incorrectly on
> FreeBSD 11 for tested postgres versions 10-13 (at least). e.g.=20

This is kind of an unhelpful bug report: you did not show what results
you got, nor what you expected to get.

           regards, tom lane

--Apple-Mail-5CCA9BF3-0C21-481B-81BE-658C4C65CC5E
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Apologies - please find screencaps and cont=
ext at the following<div><br></div><div>-&nbsp;<a href=3D"https://postgreste=
am.slack.com/archives/C0FS3UTAP/p1603440839348800">https://postgresteam.slac=
k.com/archives/C0FS3UTAP/p1603440839348800</a></div><div>-&nbsp;<a href=3D"h=
ttps://topanswers.xyz/transcript?room=3D2&amp;id=3D78663&amp;year=3D2020&amp=
;month=3D10#c78663">https://topanswers.xyz/transcript?room=3D2&amp;id=3D7866=
3&amp;year=3D2020&amp;month=3D10#c78663</a><br><br>By way of description - I=
P address/netmask pairs given in pg_hba.conf are not read into the system vi=
ew pg_hba_file_rules even in well formed and default installations. The shel=
l commands given in the initial email are meant to give a minimum reproducti=
on of this behavior when executed on FreeBSD 11</div><div><br></div><div>A d=
efault install on RHEL querying pg_hba_file_rules would show corresponding n=
on-null values as appropriate</div><div><br></div><div>Kind regards</div><di=
v><br><div dir=3D"ltr"><div>Peter Vandivier</div><div>Sent from my iPhone</d=
iv><div>Please excuse typos and brevity</div></div><div dir=3D"ltr"><br>On N=
ov 2, 2020, at 22:15, Tom Lane &lt;tgl@sss.pgh.pa.us&gt; wrote:<br><br></div=
><div dir=3D"ltr">=EF=BB=BF<span>PG Bug reporting form &lt;noreply@postgresq=
l.org&gt; writes:</span><br><blockquote type=3D"cite"><span>pg_hba_file_rule=
s reports NULL address and netmask values incorrectly on</span><br></blockqu=
ote><blockquote type=3D"cite"><span>FreeBSD 11 for tested postgres versions 1=
0-13 (at least). e.g. </span><br></blockquote><span></span><br><span>This is=
 kind of an unhelpful bug report: you did not show what results</span><br><s=
pan>you got, nor what you expected to get.</span><br><span></span><br><span>=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;regards, tom lane</span><br></div>=
</div></body></html>=

--Apple-Mail-5CCA9BF3-0C21-481B-81BE-658C4C65CC5E--