| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Remove obsolete RECHECK keyword completely |
| Date: | 2024-08-02 10:41:06 |
| Message-ID: | 113ef2d2-3657-4353-be97-f28fceddbca1@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I propose to remove the obsolete RECHECK keyword completely. This used
to be part of CREATE OPERATOR CLASS and ALTER OPERATOR FAMILY, but it
has done nothing (except issue a NOTICE) since PostgreSQL 8.4. Commit
30e7c175b81 removed support for dumping from pre-9.2 servers, so this no
longer serves any need, it seems to me.
This now removes it completely, and you'd get a normal parse error if
you used it.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Remove-obsolete-RECHECK-keyword-completely.patch | text/plain | 6.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-08-02 11:03:06 | Re: Conflict detection and logging in logical replication |
| Previous Message | Kirill Reshke | 2024-08-02 10:30:45 | Re: Small refactoring around vacuum_open_relation |