Re: range_agg

From: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-03-17 04:52:12
Message-ID: CA+renyWfVue-XQOxztE5RUOfTmffC2O6jqkmkgMcVhRUK5Y-vg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 14, 2020 at 11:13 AM Paul A Jungwirth
<pj(at)illuminatedcomputing(dot)com> wrote:
> I think that should fix the cfbot failure.

I saw this patch was failing to apply again. There was some
refactoring to how polymorphic types are determined. I added my
changes for anymultirange to that new approach, and things should be
passing again.

Yours,
Paul

Attachment Content-Type Size
v14-multirange.patch application/octet-stream 318.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey M. Borodin 2020-03-17 05:20:11 Re: [PATCH] Btree BackwardScan race condition on Standby during VACUUM
Previous Message Amit Kapila 2020-03-17 04:22:00 Re: error context for vacuum to include block number