| 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-08-16 19:55:21 |
| Message-ID: | CA+renyXD-5RKJp1VG1+9tD+sJ8Xi_MZ0XHPkv0021fV5V6uOpw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jul 5, 2020 at 12:11 PM Paul A Jungwirth
<pj(at)illuminatedcomputing(dot)com> wrote:
> I haven't made much progress storing on-disk multiranges without the
> range type oids.
Here is a patch using the TOAST EXTENDED infrastructure to store
multiranges on disk with a new "short" range type struct that omits
the range type oids, but then loads ordinary range structs for its
in-memory operations. One nice thing that fell out from that work is
that I can build an ordinary RangeType ** list at the same time.
(Since RangeTypes are varlena and their bounds may be varlena, you
already needed to get a list like that for nearly any operation.)
This is rebased on the current master, including some changes to doc
tables and pg_upgrade handling of type oids.
Yours,
Paul
| Attachment | Content-Type | Size |
|---|---|---|
| v21-multirange.patch | application/octet-stream | 427.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-16 20:17:23 | Re: Improving connection scalability: GetSnapshotData() |
| Previous Message | Andres Freund | 2020-08-16 19:00:12 | Re: Improving connection scalability: GetSnapshotData() |