Hi,
Both the UUID data type and UUID functions pages define an index entry
for "UUID" that points to the data type section. As a result, the index
includes two identical entries linking to the UUID type docs,
which seems strange.
I believe the UUID functions page should instead define its own in
To make it more consumable.
--
- Founder - https://commandprompt.com/ - 24x7x365 Postgres since 1997
- Founder and Co-Chair - https://postgresconf.org/
- Founder - https://postgresql.us - United States PostgreSQL
- Public speaker, published author, postgresql expert, and people
be
On Fri, Jun 20, 2025 at 12:33 PM Joshua Drake wrote:
> To make it more consumable.
>
Overall I'm good with the attempt to trim, and most of the changes, but
feel it tries to hard and ends up being to "matter-of-fact"; the
conjunctions that exist make reading a wall of text easier. I agree that
I wrote:
> Another thing I just remembered (think I knew it once) is the
> behavior of the first form when low > high. It's not an error!
So concretely, how about the attached? In addition to what we
mentioned so far, I made the sentence about out-of-range cases
more explicit.
>
> Overall I'm good with the attempt to trim, and most of the changes, but
> feel it tries to hard and ends up being to "matter-of-fact"; the
> conjunctions that exist make reading a wall of text easier. I agree that
> some of them could be removed as being more judgemental than mechanical.
>
Fa
On Fri, Jun 20, 2025 at 11:33 PM Fujii Masao
wrote:
>
> Hi,
>
> Both the UUID data type and UUID functions pages define an index entry
> for "UUID" that points to the data type section. As a result, the index
> includes two identical entries linking to the UUID type docs,
> which seems strange.
>
On Fri, Jun 20, 2025 at 2:21 PM Joshua Drake wrote:
>
>
>> "We advise users who to read this chapter carefully ..." ? botched
>> surgery on this one
>>
>
> Not sure what you mean here? I reviewed the source sgml (that I modified):
>
> We advise users who to read this chapter carefully because it
