Re: WIP: Enhanced ALTER OPERATOR

From: Uriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: Enhanced ALTER OPERATOR
Date: 2015-05-18 14:44:16
Message-ID: 2294424.J96ZOUA4JB@dinodell
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday 18 May 2015 10:21:10 Tom Lane wrote:
> There are fairly significant reasons why we have not done this, based
> on the difficulty of updating existing cached plans that might have
> incidentally depended on those operator properties during creation.
> Perhaps it's all right to simply ignore such concerns, but I would like
> to see a defense of why.

Then need to prohibit the use of shells operators (stub operators) to create
self-linkage. Implicitly changing commutators and negators working for a long
time through the shell operators.

> On a more practical level, please change the syntax so that it does
> not require making all those things into keywords.

Do you say about CREATE OPERATOR like syntax?

Thanks.

--
Uriy Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-05-18 14:58:42 Re: pg_upgrade cleanup
Previous Message Ryan Pedela 2015-05-18 14:41:39 Re: jsonb concatenate operator's semantics seem questionable