Re: [PATCH] Optional OR REPLACE in CREATE OPERATOR statement

2023-03-21 Thread Gregory Stark (as CFM)
On Tue, 5 Jul 2022 at 11:29, Tom Lane wrote: > > No, that's not acceptable. CREATE OR REPLACE should always produce > exactly the same final state of the object, but in this case we cannot > change the underlying function if the operator already exists. It sounds like this patch isn't the direct

Re: [PATCH] Optional OR REPLACE in CREATE OPERATOR statement

2022-07-05 Thread Tom Lane
=?UTF-8?B?U3ZldGxhbmEgRGVyZXZ5YW5rbw==?= writes: > It seems useful to have [OR REPLACE] option in CREATE OPERATOR statement, as > in CREATE FUNCTION. This option may be good for writing extension update > scripts, to avoid errors with re-creating the same operator. No, that's not acceptable. C