| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org> |
| Subject: | Re: range_agg |
| Date: | 2020-04-11 16:36:37 |
| Message-ID: | CA+renyXVz0hUmqhD5iHUZixcpNm3wrBVFqV3ewTPEe7vx9EBGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 10, 2020 at 8:44 PM Paul A Jungwirth
<pj(at)illuminatedcomputing(dot)com> wrote:
> Thanks, and thanks for your v17 also. Here is a patch building on that
> and adding support for anycompatiblemultirange.
Here is a v19 that just moved the multirange tests to a new parallel
group to avoid a max-20-tests error. Sorry about that!
Btw I'm working on typanalyze + selectivity, and it seems like the
test suite doesn't run those things? At least I can't seem to get it
to call the existing range typanalyze functions. Those would run from
the vacuum process, not an ordinary backend, right? Is there a
separate test suite for that I'm overlooking? I'm sure I can figure it
out, but since I'm uploading a new patch file I thought I'd ask. . . .
Thanks,
Paul
| Attachment | Content-Type | Size |
|---|---|---|
| v19-multirange.patch | application/octet-stream | 364.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2020-04-11 16:42:44 | Re: range_agg |
| Previous Message | Mark Dilger | 2020-04-11 16:28:03 | Re: cleaning perl code |