From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
---|---|
To: | Uriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP: Enhanced ALTER OPERATOR |
Date: | 2015-07-14 15:22:26 |
Message-ID: | 55A52932.5010606@iki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/13/2015 03:43 PM, Uriy Zhuravlev wrote:
> Hello hackers.
>
> Attached is a new version of patch:
> * port syntax from NULL to truth NONE
> * fix documentation (thanks Heikki)
> * rebase to master
Thanks, committed after some editing. I put all the logic into
AlterOperator function, in operatorcmds.c, rather than pg_operator.c. I
think that's how we've lately organized commands. I also simplified the
code quite a bit - I think you had copy-pasted from one of the generic
ALTER variants, like AlterOwnerStmt, which was overly generic for ALTER
OPERATOR. No need to look up the owner/name attributes dynamically, etc.
There was one genuine bug that I fixed: the ALTER OPERATOR command
didn't check all the same conditions that CREATE OPERATOR did, namely
that only binary operators can have join selectivity, and that only
boolean operators can have restriction/join selectivity.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Uriy Zhuravlev | 2015-07-14 15:42:31 | Re: WIP: Enhanced ALTER OPERATOR |
Previous Message | Thom Brown | 2015-07-14 15:05:00 | Re: Support retrieving value from any sequence |