| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Cosmetic improvements in ltree code. |
| Date: | 2020-03-29 23:14:24 |
| Message-ID: | E1jIh8K-0004CJ-AV@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Cosmetic improvements in ltree code.
Add more comments in ltree.h, and correct a misstatement or two.
Use a symbol, rather than hardwired constants, for the maximum length
of an ltree label. The max length is still hardwired in the associated
error messages, but I want to clean that up as part of a separate patch
to improve the error messages.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/2743d9ae4a490a7d96b5c19d50694bd101a87dc8
Modified Files
--------------
contrib/ltree/ltree.h | 41 +++++++++++++++++++++++++++++++----------
contrib/ltree/ltree_io.c | 19 ++++++++++++++-----
2 files changed, 45 insertions(+), 15 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-03-30 02:08:46 | Re: pgsql: Allow vacuum command to process indexes in parallel. |
| Previous Message | Tom Lane | 2020-03-29 22:54:43 | pgsql: Doc: correct misstatement about ltree label maximum length. |