| From: | Svetlana Derevyanko <s(dot)derevyanko(at)postgrespro(dot)ru> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | [PATCH] Optional OR REPLACE in CREATE OPERATOR statement |
| Date: | 2022-07-05 08:40:23 |
| Message-ID: | 1657010423.184452823@f275.i.mail.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello hackers,
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.
Because of cached query plans, only RESTRICT and JOIN options can be changed for existing operator, as in ALTER OPERATOR statement.
(discussed here: https://www.postgresql.org/message-id/flat/3348985.V7xMLFDaJO%40dinodell )
The attached patch will be proposed for September CF.
Best regards,
--
Svetlana Derevyanko
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-optional-OR-REPLACE-in-CREATE-OPERATOR-statem.patch | text/x-diff | 17.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2022-07-05 08:41:51 | Re: logical replication restrictions |
| Previous Message | Dilip Kumar | 2022-07-05 08:32:42 | Re: making relfilenodes 56 bits |