Re: postgres_fdw: another oddity in costing aggregate pushdown paths

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Antonin Houska <ah(at)cybertec(dot)at>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgres_fdw: another oddity in costing aggregate pushdown paths
Date: 2019-05-09 09:52:38
Message-ID: CAPmGK14GPPortu8sOnganQpL0ufNaut46esOZJHo2=fMvQvLxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 8, 2019 at 12:45 PM Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> This doesn't get applied cleanly after commit 1d33858406. Here is a
> rebased version of the patch. I also modified the comments a little
> bit. If there are no objections from Antonin or anyone else, I'll
> commit the patch.

Pushed. Thanks for reviewing, Antonin!

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-05-09 10:23:25 Re: Fixing order of resowner cleanup in 12, for Windows
Previous Message Pavel Stehule 2019-05-09 09:12:09 Re: pgsql: Add strict_multi_assignment and too_many_rows plpgsql checks