Re: fix for BUG #3720: wrong results at using ltree - Mailing list pgsql-hackers

From Benjie Gillam
Subject Re: fix for BUG #3720: wrong results at using ltree
Date
Msg-id 157415927562.29912.5497068377906958040.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: fix for BUG #3720: wrong results at using ltree  (Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>)
List pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world:  tested, passed
Implements feature:       tested, passed
Spec compliant:           not tested
Documentation:            tested, failed

This is my first PostgreSQL commitfest and review, guidance welcome.

This patch is straightforward, it applies cleanly, and it includes tests (I've also tested the feature manually).

The (existing) documentation states "The length of a label path must be less than 65kB," I believe that the 65kB
mentionedhere should instead be 64kB - perhaps the patch could be updated with this single-character fix? At first I
thoughtthe 65kB limit would be applied to the label path string (e.g. 'Top.Countries.Europe.Russia' would be 27 bytes),
butit seems the limit applies to the number of labels in the path - perhaps `kB` is not the right measurement here and
itshould explicitly state 65536?
 

It is not stated in the documentation what should happen if the label path length is greater than 65535, so raising an
errormakes sense (but may be a breaking change). 

The new status of this patch is: Waiting on Author

pgsql-hackers by date:

Previous
From: Rushabh Lathia
Date:
Subject: Re: backup manifests
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Protect syscache from bloating with negative cache entries