Re: [PATCH] Optional OR REPLACE in CREATE OPERATOR statement
Gregory Stark (as CFM) <stark.cfm@gmail.com>
From: "Gregory Stark (as CFM)" <stark.cfm@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Svetlana Derevyanko <s.derevyanko@postgrespro.ru>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-03-22T03:29:12Z
Lists: pgsql-hackers
On Tue, 5 Jul 2022 at 11:29, Tom Lane <tgl@sss.pgh.pa.us> 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 direction to go in. I don't know if IF NOT EXISTS is better but that design discussion should probably happen after this commitfest. I'm sorry but I guess I'll mark this patch Rejected. -- Gregory Stark As Commitfest Manager