pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: y.saburov@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Table 9.46. UUID Extraction Functions
Date: Fri, 09 Oct 2026 20:25:16 -0400
Message-ID: <30956.1791591916@sss.pgh.pa.us> (raw)
In-Reply-To: <176ada94989db19564e580b48c2b44be94a06d3e.camel@cybertec.at>
References: <179143326813.1061054.14714458907175925072@wrigleys.postgresql.org>
	<15c6905385e3ca36756eefd06e73be57c9e6ae72.camel@cybertec.at>
	<2519947.1791477667@sss.pgh.pa.us>
	<419b7321d71f70a9390ea6a958525468473ba8c3.camel@cybertec.at>
	<2558476.1791516774@sss.pgh.pa.us>
	<d16be0c5e1f60366dfdc181b0ebd5cf2d213ecf7.camel@cybertec.at>
	<2565626.1791524131@sss.pgh.pa.us>
	<176ada94989db19564e580b48c2b44be94a06d3e.camel@cybertec.at>

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> 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.

Ah, excellent point.  If we consider only fragments of SQL then yes,
the problem gets way smaller.

> 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...

Dunno, I'm not seeing a warning there either.  Perhaps that zwsp
dates from before one of the mass reformattings we've done over
the years?  I didn't bother doing any archaeology 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.

Great idea, but when I looked at the rendered A4 PDF I saw why we'd
put in the zwsps: without them, FOP decides that the best way
to break these lines is like

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

which of course is really horrid (cf first attached screenshot).
However, adapting your idea a bit, I tried putting spaces around
the "::", and that renders far better (cd second attachment).
So I'll run with that.

			regards, tom lane

Attachments:

table-9.47-v1.png (image/png, 188.4K) download view image
table-9.47-v2.png (image/png, 184.3K) download view image

view thread (12+ messages)  latest in thread

Message-ID: <30956.1791591916@sss.pgh.pa.us>
Permalink:  ../30956.1791591916@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/30956.1791591916@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, laurenz.albe@cybertec.at, y.saburov@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: Table 9.46. UUID Extraction Functions
  In-Reply-To: <30956.1791591916@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox