Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9FZ6-0000GA-PY for pgsql-docs@arkaria.postgresql.org; Fri, 21 Aug 2020 22:31:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k9FZ5-0004Le-Nn for pgsql-docs@arkaria.postgresql.org; Fri, 21 Aug 2020 22:31:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9FZ5-0004LU-Hy for pgsql-docs@lists.postgresql.org; Fri, 21 Aug 2020 22:31:15 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9FZ3-0001jE-If for pgsql-docs@lists.postgresql.org; Fri, 21 Aug 2020 22:31:14 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1k9FZ2-0002Di-NA; Fri, 21 Aug 2020 18:31:12 -0400 Date: Fri, 21 Aug 2020 18:31:12 -0400 From: Bruce Momjian To: =?iso-8859-1?Q?J=FCrgen?= Purtz Cc: pgsql-docs@lists.postgresql.org Subject: Re: obsolete indexing method "rtree" Message-ID: <20200821223112.GI13363@momjian.us> References: <9cda4603-76d0-b063-5dc3-a9a99506340b@purtz.de> <2510904.1596636088@sss.pgh.pa.us> <15ec5428-d46a-1725-f38d-44986a977abb@purtz.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <15ec5428-d46a-1725-f38d-44986a977abb@purtz.de> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Aug 7, 2020 at 05:46:45PM +0200, Jürgen Purtz wrote: > > On 06.08.20 10:12, David G. Johnston wrote: > > On Thu, Aug 6, 2020 at 12:18 AM Jürgen Purtz wrote: > > > > Why? > > Because it can hinder the learning process. > > > FWIW I'd at least fixup comment.sgml to reference a current type.  And > while in there might as well add missing examples for the following since > we seem to have a goal of providing one example for every syntax (operators > get two in order to show NONE, rightarg). > >   EVENT TRIGGER object_name | >   PUBLICATION object_name | >   SUBSCRIPTION object_name | >   ROUTINE routine_name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ] > |   > > Such a "make current" patch that covers this complaint seems reasonable; > IOW, why not if you are in there anyway - rtree has some baggage and no > particular merit such that a different label would be worse. > > I don't see the value of removing the backward compatibility hack if it's > not bothering the developers.  Whether the documentation should be changed > to basically only cover this and nothing more I cannot say without studying > said documentation.  I agree with the general motive though. > > David J. > > > Patch with four additional comments and one modified comment attached. Thanks, patch applied through 11. We added ROUTINE/PROCEDURE in PG 11, so I decided not to cherry pick items to be applied prior to that release. Thanks. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee