| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove obsolete RECHECK keyword completely |
| Date: | 2024-08-09 05:27:53 |
| Message-ID: | ba7e0f19-7a80-450f-a7ca-ab30ba85856d@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05.08.24 15:44, Aleksander Alekseev wrote:
>> 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.
>
> I reviewed and tested the code. LGTM.
committed, thanks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-08-09 05:49:12 | Re: [bug fix] prepared transaction might be lost when max_prepared_transactions is zero on the subscriber |
| Previous Message | Amit Kapila | 2024-08-09 05:12:58 | Re: Found issues related with logical replication and 2PC |