Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t1Eum-00FJZv-8O for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Oct 2024 01:02:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t1Euk-00DZpL-Gl for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Oct 2024 01:02:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t1Euk-00DZpA-7H for pgsql-hackers@lists.postgresql.org; Thu, 17 Oct 2024 01:02:54 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t1Euf-001Rx3-Lw for pgsql-hackers@postgresql.org; Thu, 17 Oct 2024 01:02:53 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description; bh=HWJa5N8yzli28m1QL5mT4H2p9LjGIDZDAkJL3CGZNkI=; b=DrSAe SlfiIT4MH2263nPW+exVqCVhZGFE17pIo5sz0w9cj2l8QSUwipF6CUDef0+kf9r+N03KXmzE3+fCu JNBNqBWhSRfvbRw/khQxyPnQC5au+jRwFA+cb8nyuBTQ7/Gkjp8zxatY8c3ksXbtB7dbS1qLWHoCt 24SVB/7XoAGieisyQXKTINOCiDyFzWU30+JsLoWGB7rIuXByQ/2kb/9hCWc2Mmt8KiFaNDniXJElO 6cehIaXlzHR9ObBAljR3Rd9jpxxaGePBfZTc6ZtSjXr0vgvrVceLtAFMQxfFqZ08FD9pYFOCc92dQ 2zBbfpVEjy57BQHqGBxL+uIkdABeQ==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1t1Eue-009tuK-0p; Wed, 16 Oct 2024 21:02:48 -0400 Date: Wed, 16 Oct 2024 21:02:48 -0400 From: Bruce Momjian To: pierre@vennin.net, PostgreSQL-development Subject: Re: ltree docs imprecise about sorting order Message-ID: References: <171648107027.2021729.14071096098945602529@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <171648107027.2021729.14071096098945602529@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, May 23, 2024 at 04:17:50PM +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/ltree.html > Description: > > The ltree docs available at > https://www.postgresql.org/docs/current/ltree.html state "Comparison sorts > in the order of a tree traversal" without specifying the strategy > implemented to walk the tree. > A quick experiment suggests that the implemented solution is pre-ordered > depth-first search. > I suggest the ltree docs be amended to "Comparison sorts in the order of a > pre-ordered depth-first tree traversal". [ moved to hackers ] Can someone confirm this and/or create a patch? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com When a patient asks the doctor, "Am I going to die?", he means "Am I going to die soon?"