pgsql: Remove hstore's text => text operator. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Remove hstore's text => text operator.
Date
Msg-id E1RNbmt-0007Do-20@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Remove hstore's text => text operator.  (Thom Brown <thom@linux.com>)
Re: pgsql: Remove hstore's text => text operator.  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-committers
Remove hstore's text => text operator.

Since PostgreSQL 9.0, we've emitted a warning message when an operator
named => is created, because the SQL standard now reserves that token
for another use.  But we've also shipped such an operator with hstore.
Use of the function hstore(text, text) has been recommended in
preference to =>(text, text).  Per discussion, it's now time to take
the next step and stop shipping the operator.  This will allow us to
prohibit the use of => as an operator name in a future release if and
when we wish to support the SQL standard use of this token.

The release notes should mention this incompatibility.

Patch by me, reviewed by David Wheeler, Dimitri Fontaine and Tom Lane.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/b60653bc0b75b7f3b5dda0a2968a22129aafb2b2

Modified Files
--------------
contrib/hstore/Makefile             |    3 +-
contrib/hstore/hstore--1.0--1.1.sql |    7 +
contrib/hstore/hstore--1.1.sql      |  524 +++++++++++++++++++++++++++++++++++
contrib/hstore/hstore.control       |    2 +-
doc/src/sgml/hstore.sgml            |   17 +-
5 files changed, 535 insertions(+), 18 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Make VACUUM avoid waiting for a cleanup lock, where possible.
Next
From: Peter Eisentraut
Date:
Subject: pgsql: -DLINUX_OOM_ADJ=0 should be in CPPFLAGS, not CFLAGS