Re: Row pattern recognition

Vik Fearing <vik@postgresfriends.org>

From: Vik Fearing <vik@postgresfriends.org>

To: Jacob Champion <jchampion@timescale.com>, Tatsuo Ishii <ishii@sraoss.co.jp>

Cc: pgsql-hackers@postgresql.org

Date: 2023-07-21T00:07:44Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add temporal FOREIGN KEY contraints
- 89f908a6d0ac 18.0 cited
Remove obsolete executor cleanup code
- d060e921ea5a 17.0 cited

On 7/21/23 01:36, Jacob Champion wrote:
> There's also the issue of backtracking in the face of reclassification,
> as I think Vik was alluding to upthread.

We definitely need some kind of backtracking or other reclassification 
method.

> (I've attached two failing tests against v2, to hopefully better
> illustrate, along with what I_think_  should be the correct results.)

Almost.  You are matching 07-01-2023 but the condition is "price > 100".
-- 
Vik Fearing