From: Jürgen Purtz <juergen@purtz.de>
To: pgsql-docs@lists.postgresql.org
Subject: Re: obsolete indexing method "rtree"
Date: Thu, 6 Aug 2020 09:18:35 +0200
Message-ID: <e1a6fe18-b4f1-3d4e-8788-ced8c08e086a@purtz.de> (raw)
In-Reply-To: <2510904.1596636088@sss.pgh.pa.us>
References: <9cda4603-76d0-b063-5dc3-a9a99506340b@purtz.de>
<2510904.1596636088@sss.pgh.pa.us>
> Why?
Because it can hinder the learning process. And it's possible that
people ignore or forget about the warning message, but are confused
somewhat later that commands like \d shows GiST instead of RTREE.
> It's not hurting anything to continue the substitution in CREATE
> INDEX.
Yes, it's not hurting. But it makes the life of newcomers a little
harder. Why not stripping away thinks which aren't used since 12 years?
> Possibly the comment in seg.sgml should be adjusted to refer to GiST
> indexes --- but then again, it's not entirely clear whether it's even
> still relevant for GiST indexes.
This comment is not specific to the old rtree implementation. In
general, the input to R-Trees and the algorithm which creates the
'rectangles' in non-leaf nodes influences the building of the tree and
hereinafter the performance of access methods.
> Perhaps it's talking about a deficiency
> that was specific to the old rtree code.
And sometimes even experts have to spend time thinking about the situation.
Nevertheless, this is a tiny issue. Unfortunately I don't have the
knowledge to modify the C-source and create a patch.
--
Jürgen Purtz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: juergen@purtz.de, pgsql-docs@lists.postgresql.org
Subject: Re: obsolete indexing method "rtree"
In-Reply-To: <e1a6fe18-b4f1-3d4e-8788-ced8c08e086a@purtz.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox