From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Subject: | Deprecating postfix and factorial operators in PostgreSQL 13 |
Date: | 2020-08-27 16:13:49 |
Message-ID: | BE2DF53D-251A-4E26-972F-930E523580E9@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hackers,
Over in [1] we have been discussing the deprecation of postfix operators, with the general consensus that deprecation warnings should be included in this upcoming release and postfix operator support should be removed in PostgreSQL 14. Since not all people who follow -hackers will necessarily have been following that thread, I am creating this new thread, with a patch which adds the deprecation notices, for your consideration.
The only postfix operator we ship in the standard catalogs is the factorial operator (!), which is deprecated by this patch.
The standard catalogs also include a prefix factorial operator (!!) which has been deprecated since 2011.
The deprecation warnings included in this patch warn that postfix operator support, along with both postfix ! and prefix !! factorial operators, will be removed in PostgreSQL 14.
Some of the deprecation verbiage supplied by John Naylor, some by me:
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Adding-deprecation-notices.patch | application/octet-stream | 9.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-08-27 16:16:22 | Re: Deprecating postfix and factorial operators in PostgreSQL 13 |
Previous Message | Alvaro Herrera | 2020-08-27 16:09:55 | Re: [POC]Enable tuple change partition caused by BEFORE TRIGGER |