| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(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 23:29:30 |
| Message-ID: | 41e1c5147c95838a3c4bd31dc03d258193f3c4b0.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2023-01-26 at 22:39 +0100, Peter Eisentraut wrote:
> 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.
I am using these GUCs for testing the various collation paths in my
collation refactoring branch.
I find them pretty useful, and when I saw a regression, I thought
others might think it was useful, too. But if not I'll just leave them
in my branch and withdraw from this thread.
--
Jeff Davis
PostgreSQL Contributor Team - AWS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2023-01-26 23:36:52 | Re: New strategies for freezing, advancing relfrozenxid early |
| Previous Message | Tom Lane | 2023-01-26 23:04:42 | Re: Something is wrong with wal_compression |