From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Cross-type index comparison support in contrib/btree_gin |
Date: | 2025-02-07 22:41:32 |
Message-ID: | 1733979.1738968092@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> I forgot to mention a couple of questions for review:
> Should we adjust the documentation of comparePartial() to promise
> explicitly that partial_key is the same datum returned by extractQuery?
> By my reading, it kind of implies that, but it's not quite black and
> white.
> In the 0005 patch, I relied on date2timestamp_opt_overflow and
> its siblings where available. But some of the conversions such
> as timestamptz-to-timestamp don't have one of those, so I was
> forced to copy-and-paste some fairly low-level code. Would it
> make sense to refactor the related core routines to expose
> xxx2yyy_opt_overflow interfaces, extending what 5bc450629 and
> 52ad1e659 did?
After further review it seems like both of those things would be
improvements, so here's a v2 that does it like that. This also
adds a PG_USED_FOR_ASSERTS_ONLY marker whose lack was pointed
out by the cfbot; no other meaningful changes.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Break-out-xxx2yyy_opt_overflow-APIs-for-more-date.patch | text/x-diff | 9.4 KB |
v2-0002-Preliminary-refactoring.patch | text/x-diff | 7.6 KB |
v2-0003-Add-cross-type-comparisons-for-integer-types.patch | text/x-diff | 35.6 KB |
v2-0004-Add-cross-type-comparisons-for-float-types.patch | text/x-diff | 11.6 KB |
v2-0005-Add-cross-type-comparisons-for-string-types.patch | text/x-diff | 8.3 KB |
v2-0006-Add-cross-type-comparisons-for-datetime-types.patch | text/x-diff | 33.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | James Hunter | 2025-02-07 22:43:12 | Re: should we have a fast-path planning for OLTP starjoins? |
Previous Message | Nathan Bossart | 2025-02-07 22:27:23 | describe special values in GUC descriptions more consistently |