| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-07-05 19:11:15 |
| Message-ID: | CA+renyVKHWNiFvaoPW1B_3mafhbcwm7zzc9T3xp9+RZ1D+tsXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jul 5, 2020 at 10:20 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>
> This needs to be rebased ; set cfbot to "waiting".
Here is a patch that is rebased onto current master. It also includes
the analyze/selectivity additions.
I haven't made much progress storing on-disk multiranges without the
range type oids. Peter Geoghegan suggested I look at how we handle
arrays in heap_deform_tuple, but I don't see anything there to help me
(probably I misunderstood him though). Just knowing that arrays are
something we do this for is enough to hunt for clues, but if anyone
can point me more directly to code that will help me do it for
multiranges, I'd be appreciative.
Yours,
Paul
| Attachment | Content-Type | Size |
|---|---|---|
| v20-multirange.patch | application/x-patch | 412.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2020-07-05 19:25:49 | Re: range_agg |
| Previous Message | Thomas Kellerer | 2020-07-05 19:08:07 | Re: Persist MVCC forever - retain history |