Re: [PATCH] Expand character set for ltree labels
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Garen Torikian <gjtorikian@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2023-01-06T21:08:29Z
Lists: pgsql-hackers
On 2023-01-06 Fr 11:29, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.net> writes: >> Regardless of the punycode issue, allowing hyphens in ltree labels seems >> quite reasonable. I haven't reviewed the patch yet, but if it's OK I >> intend to commit it. > No objection to allowing hyphens. If we're going to increase the length > limit, how about using 1000 characters? AFAICS we could even get away > with 10K, but it's probably best to hold a bit or two in reserve in case > we ever want flags or something associated with labels. > OK, done that way. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
Allow hyphens in ltree labels
- b1665bf01e5f 16.0 landed
-
Check that xmax didn't commit in freeze check.
- eb5ad4ff05fd 16.0 cited
-
Push lpp variable closer to usage in heapgetpage()
- e351f8541831 16.0 cited
-
tests: Restrict pg_locks queries in advisory_locks.sql to current database
- c3315a7da57b 16.0 cited