Re: Window Function "Run Conditions"

From: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Window Function "Run Conditions"
Date: 2022-04-05 07:40:29
Message-ID: CAKU4AWrC8hcwXx7S1VyWYLcdYp6R8f0JfkgvqmUYwXBQ5yLvTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> The root cause is even ExecQual(winstate->runcondition, econtext) return
> false, we
> still return the slot to the upper node. A simple hack can avoid it.
>

Forget to say 0002 shows what I mean.

--
Best Regards
Andy Fan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-04-05 07:41:28 Re: Skipping logical replication transactions on subscriber side
Previous Message Andy Fan 2022-04-05 07:38:44 Re: Window Function "Run Conditions"