Re: Partial aggregates pushdown - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Partial aggregates pushdown
Date
Msg-id 4012625.1701120204@sss.pgh.pa.us
Whole thread Raw
In response to Re: Partial aggregates pushdown  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Partial aggregates pushdown
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Nov 27, 2023 at 3:59 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> TBH, I think this entire proposal is dead in the water.  Which is
>> sad from a performance standpoint, but I can't see any way that
>> we would not regret shipping a feature that makes such assumptions.

> I think it's ridiculous to just hold our breath and pretend like this
> feature isn't needed -- it's at least half a decade overdue. We engage
> in endless hand-wringing over local-remote symmetry in cases where
> other systems seem to effortlessly make that assumption and then get
> on with building new features.

Well, one of the founding principles of postgres_fdw was to be able
to talk to PG servers that are not of the same version as yours.
If we break that in the name of performance, we are going to have
a lot of unhappy users.  Even the ones who do get the benefit of
the speedup are going to be unhappy when it breaks because they
didn't upgrade local and remote at exactly the same time.

Just because we'd like to have it doesn't make the patch workable
in the real world.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: autovectorize page checksum code included elsewhere
Next
From: Magnus Hagander
Date:
Subject: Re: proposal: change behavior on collation version mismatch