Re: Deprecating postfix and factorial operators in PostgreSQL 13 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Deprecating postfix and factorial operators in PostgreSQL 13
Date
Msg-id CA+TgmoYUD5J4BoW-SeJVBULvybiRjsrvWbNcyG5bUX_nfYir_A@mail.gmail.com
Whole thread Raw
In response to Re: Deprecating postfix and factorial operators in PostgreSQL 13  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: Deprecating postfix and factorial operators in PostgreSQL 13
List 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



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: new heapcheck contrib module
Next
From: Gilles Darold
Date:
Subject: Re: New default role- 'pg_read_all_data'