Re: Table 9.46. UUID Extraction Functions

On Fri, 2026-10-09 at 01:35 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > On Thu, 2026-10-08 at 23:32 -0400, Tom Lane wrote:
> > > I still wonder whether there's another solution path though.
> > > We settled on &zwsp; because it fixed the major issue here,
> > > but that doesn't mean there isn't a better answer.
>
> > I think that an improved version could look as follows:
>
> > uuid_extract_timestamp(
> > '019535d9-3df7-79fb-b466-fa907fa17f9e'::uuid
> > ) → 2025-02-23 21:46:24.503-05
>
> Hmm, yeah, that could work so far as the PDF line-break problem
> is concerned. Would it look too odd to HTML readers?
>
> > Also, not everything (query results etc.) are likely to be copied and
> > pasted by users. So I guess the way forward would be for me to spend
> > some time with this. But then - is it *that* important?
>
> Yup, that. If you want to press forward, have at it; I'm willing
> to push fixes in this area.

I felt inspired enough to take a look, and I found only three places
that looked like likely things that someone might copy and paste.

The first didn't actually need a line break in either the US letter
or A4 format, so I simply removed the &zwsp;. I wonder if some other
documentation format might need it though...

For the UUID functions that the complaint was about, I simply added
regular spaces inside the parentheses, which in HTML looks like

uuid_extract_version( '41db1265-8bc1-4ab3-992f-885799a4af1d'::uuid ) → 4

I'd say that that is acceptable.

Yours,
Laurenz Albe