Re: SQL:2011 application time

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Subject: Re: SQL:2011 application time
Date: 2023-07-04 12:48:48
Message-ID: 251B44D1-D3E0-47E4-AB9D-4A848EDB495E@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 8 May 2023, at 09:10, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 03.05.23 23:02, Paul Jungwirth wrote:
>> Thank you again for the review. Here is a patch with most of your feedback addressed. Sorry it has taken so long! These patches are rebased up to 1ab763fc22adc88e5d779817e7b42b25a9dd7c9e
>> (May 3).
>
> Here are a few small fixup patches to get your patch set compiling cleanly.
>
> Also, it looks like the patches 0002, 0003, and 0004 are not split up correctly. 0002 contains tests using the FOR PORTION OF syntax introduced in 0003, and 0003 uses the function build_period_range() from 0004.

These patches no longer apply without a new rebase. Should this patch be
closed in while waiting for the prequisite of adding btree_gist to core
mentioned upthread? I see no patch registered in the CF for this unless I'm
missing sometihng.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2023-07-04 12:50:00 Re: pipe_read_line for reading arbitrary strings
Previous Message Daniel Gustafsson 2023-07-04 12:34:28 Re: [PATCH]Feature improvement for MERGE tab completion