Re: WIP: Enhanced ALTER OPERATOR

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

Uriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> writes:
> I have attached a patch that extends ALTER OPERATOR to support COMMUTATOR,
> NEGATOR, RESTRICT and JOIN.

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.

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

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ryan Pedela 2015-05-18 14:41:39 Re: jsonb concatenate operator's semantics seem questionable
Previous Message Uriy Zhuravlev 2015-05-18 14:12:22 WIP: Enhanced ALTER OPERATOR