| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Garen Torikian <gjtorikian(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Expand character set for ltree labels |
| Date: | 2023-01-06 21:08:29 |
| Message-ID: | df318c06-5df3-0ceb-5bbb-37d3c57a2598@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-01-06 Fr 11:29, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arne Roland | 2023-01-06 21:29:12 | Permute underscore separated components of columns before fuzzy matching |
| Previous Message | Thomas Munro | 2023-01-06 20:16:39 | Re: Cygwin cleanup |