| From: | Zhang Mingli <zmlpostgres(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | useless LIMIT_OPTION_DEFAULT |
| Date: | 2023-12-14 01:17:33 |
| Message-ID: | 59d61a1a-3858-475a-964f-24468c97cc67@Spark |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, all
By reading the codes, I found that we process limit option as LIMIT_OPTION_WITH_TIES when using WITH TIES
and all others are LIMIT_OPTION_COUNT by commit 357889eb17bb9c9336c4f324ceb1651da616fe57.
And check actual limit node in limit_needed().
There is no need to maintain a useless default limit enum.
I remove it and have an install check to verify.
Are there any considerations behind this?
Shall we remove it for clear as it’s not actually the default option.
Zhang Mingli
www.hashdata.xyz
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Remove-useless-LIMIT_OPTION_DEFAULT.patch | application/octet-stream | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2023-12-14 01:30:04 | Re: Synchronizing slots from primary to standby |
| Previous Message | Heikki Linnakangas | 2023-12-14 00:48:36 | Simplify newNode() |