Re: [PROPOSAL] Temporal query processing with range types - Mailing list pgsql-hackers

From Ibrar Ahmed
Subject Re: [PROPOSAL] Temporal query processing with range types
Date
Msg-id CALtqXTcLnd+taZhecg0+65M8z0CJvuvotoQxuTMAeiMyRzQs0w@mail.gmail.com
Whole thread Raw
In response to Re: [PROPOSAL] Temporal query processing with range types  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: [PROPOSAL] Temporal query processing with range types  (Peter Moser <pitiz29a@gmail.com>)
List pgsql-hackers
Hi,
I have rebased the patch and currently reviewing the patch 
on master (1e2fddfa33d3c7cc93ca3ee0f32852699bd3e012).




On Mon, Jul 1, 2019 at 4:45 PM Thomas Munro <thomas.munro@gmail.com> wrote:
On Wed, Apr 3, 2019 at 2:12 AM Ibrar Ahmed <ibrar.ahmad@gmail.com> wrote:
> I start looking at the patch, there is a couple of problems with the patch. The first one is the OID conflict, which I fixed on my machine. The second problem is assertion failure. I think you have not compiled the PostgreSQL code with the assertion.

Hi Peter,

Looks like there was some good feedback for this WIP project last time
around.  It's currently in "Needs Review" status in the July
Commitfest.  To encourage more review and see some automated compile
and test results, could we please have a fresh rebase?  The earlier
patches no longer apply.

Thanks,

--
Thomas Munro
https://enterprisedb.com


--
Ibrar Ahmed
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: The unused_oids script should have a reminder to use the 8000-8999 OID range
Next
From: Andres Freund
Date:
Subject: Re: partition routing layering in nodeModifyTable.c