"David G. Johnston" 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. Prob
On Mon, Aug 5, 2024 at 4:30 PM Tom Lane wrote:
>
> On the whole I'm inclined to do nothing here; these docs have to
> satisfy a number of requirements, and "every example should be
> copy-and-pasteable" doesn't seem like a good constraint to add.
> Another idea perhaps could be to remove enough d
PG Doc comments form writes:
> On the page:
> https://www.postgresql.org/docs/16/datatype-net-types.html#DATATYPE-CIDR
> in the "Table 8.22. cidr Type Input Examples"
> is invalid value for CIDR notation: 2001:4f8:3:ba:2e0:81ff:fe22:d1f1/128
The value is correct as displayed:
=# select '2001:4
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/datatype-net-types.html
Description:
On the page:
https://www.postgresql.org/docs/16/datatype-net-types.html#DATATYPE-CIDR
in the "Table 8.22. cidr Type Input Examples"
is invalid value f
On 12.07.2024 16:42, Tom Lane wrote:
PL/pgSQL does not support savepoints (SAVEPOINT/ROLLBACK TO
SAVEPOINT/RELEASE SAVEPOINT commands). Typical usage patterns
for savepoints can be replaced by blocks with exception handlers
(see 43.6.8). Under the hood, a block with exc
