From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: wombatbuddy@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: There is an invalid value for cidr type in the "Table 8.22. cidr
 Type Input Examples"
In-reply-to: 
 <CAKFQuwbdijdgydwQZn9n+TQ1_RMHM49sLdX-icd-1Ndpxj+ATQ@mail.gmail.com>
References: <172286815264.915373.10691480560464060561@wrigleys.postgresql.org>
 <1230606.1722900599@sss.pgh.pa.us>
 <CAKFQuwbdijdgydwQZn9n+TQ1_RMHM49sLdX-icd-1Ndpxj+ATQ@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Mon, 05 Aug 2024 16:42:53 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1232654.1722901908.1@sss.pgh.pa.us>
Date: Mon, 05 Aug 2024 19:51:48 -0400
Message-ID: <1232655.1722901908@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1232655.1722901908%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> Another option, write:
> "Same as input."
> in the other two columns - so one doesn't have to look closely at some 30
> characters of hex to prove to themselves the inputs and outputs are indeed
> identical.

Oh, I like that, if it makes the table narrow enough.  Probably need
to set it in italics or something to make it obviously not-data.

> Would do it elsewhere for consistency

Right, we'd have to do it in each entry of this table (that it
is correct for).

			regards, tom lane