| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GUCs to control abbreviated sort keys |
| Date: | 2023-01-26 21:39:30 |
| Message-ID: | b6f86f00-4cb3-ea20-67a1-a1de94061a24@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25.01.23 22:16, Jeff Davis wrote:
> I am highlighting this case because the existence of a single non-
> contrived case or regression suggests that we may want to explore
> further and tweak heuristics. That's quite natural when the heuristics
> are based on a complex dependency like a collation provider. The
> sort_abbreviated_keys GUC makes that kind of exploration and tweaking a
> lot easier.
Maybe an easier way to enable or disable it in the source code with a
#define would serve this. Making it a GUC right away seems a bit
heavy-handed. Further exploration and tweaking might well require
further source code changes, so relying on a source code level toggle
would seem appropriate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-01-26 21:46:46 | Re: run pgindent on a regular basis / scripted manner |
| Previous Message | Andrey Borodin | 2023-01-26 21:28:50 | Re: Something is wrong with wal_compression |