Re: Pulling up direct-correlated ANY_SUBLINK

From: Antonin Houska <ah(at)cybertec(dot)at>
To: Richard Guo <riguo(at)pivotal(dot)io>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pulling up direct-correlated ANY_SUBLINK
Date: 2019-09-12 15:35:21
Message-ID: 33137.1568302521@antos
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Richard Guo <riguo(at)pivotal(dot)io> wrote:

> On Wed, Sep 11, 2019 at 3:25 PM Antonin Houska <ah(at)cybertec(dot)at>
> wrote:
>
>
> Nevertheless, I don't know how to overcome the problems that I
> mentioned
> upthread.
>
>
> Do you mean the problem "the WHERE clause of the subquery didn't
> participate in the SEMI JOIN evaluation"? Good news is it has been
> fixed
> by commit 043f6ff0 as I mentioned upthread.

Do you say that my old patch (rebased) no longer breaks the regression tests?

(I noticed your other email in the thread which seems to indicate that you're
no lo longer interested to work on the feature, but asking out of curiosity.)

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-09-12 15:49:29 Re: [PATCH] Incremental sort (was: PoC: Partial sort)
Previous Message Alvaro Herrera 2019-09-12 15:19:50 Re: Implementing Incremental View Maintenance