Re: Deprecating postfix and factorial operators in PostgreSQL 13
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
pgsql-hackers <pgsql-hackers@postgresql.org>, John Naylor <john.naylor@2ndquadrant.com>,
Vik Fearing <vik@postgresfriends.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Date: 2020-08-28T15:17:12Z
Lists: pgsql-hackers
On Thu, Aug 27, 2020 at 1:07 PM Mark Dilger <mark.dilger@enterprisedb.com> wrote: > Yes, that is better. Attached. So, in this version, there are six copies of the deprecation notice John wrote, rather than just one. Maybe we need more than one, but I doubt we need six. I don't think the CREATE OPERATOR documentation needs to mention this both when first introducing the concept and then again when defining right_type; the former seems sufficient. I don't think xoper.sgml needs these changes either; they interrupt the flow of the narrative and I don't think this is where anyone would look for a deprecation notice. I would also argue for dropping the mentions in the docs for ALTER OPERATOR FAMILY and CREATE OPERATOR CLASS, although those seem less clear-cut. Really, CREATE OPERATOR where John had it originally seems like the right place. That being said, the changes to typeconv.sgml and drop_operator.sgml seem like improvements, so I'd keep those. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Mark factorial operator, and postfix operators in general, as deprecated.
- cc8a71e93084 9.5.24 landed
- d1ee6ce4c9ff 11.10 landed
- 9dee85b5b833 12.5 landed
- 1f38d3851190 10.15 landed
- 1ce20826ce80 9.6.20 landed
- 845cfe012fd1 13.0 landed
- 6ca547cf75ef 14.0 landed