| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GUCs to control abbreviated sort keys |
| Date: | 2023-01-25 21:30:07 |
| Message-ID: | 5527738835f7800a19e2b7aaafdd7c6708d99ef7.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2023-01-24 at 19:43 -0600, Justin Pryzby wrote:
> I think "an optimization, if applicable" is either too terse, or
> somehow
> wrong. Maybe:
>
> > Enables or disables the use of abbreviated keys, a sort
> > optimization...
Done.
> > + optimization could return wrong results. Set to
> > + <literal>true</literal> if certain that
> > <function>strxfrm()</function>
> > + can be trusted.
>
> "if you are certain"; or "if it is ..."
Done.
Thank you, rebased patch attached.
--
Jeff Davis
PostgreSQL Contributor Team - AWS
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Introduce-GUCs-to-control-abbreviated-keys-sort-o.patch | text/x-patch | 8.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-01-25 21:31:37 | Re: heapgettup() with NoMovementScanDirection unused in core? |
| Previous Message | Andres Freund | 2023-01-25 21:26:49 | Re: plpython vs _POSIX_C_SOURCE |