Re: BUG #18330: The query planner chooses the wrong plan when using the parallel aggregation function - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18330: The query planner chooses the wrong plan when using the parallel aggregation function
Date
Msg-id 4148241.1707092200@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18330: The query planner chooses the wrong plan when using the parallel aggregation function  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> Below is an example of queries. It shows that the query planner chooses
> sequential aggregation instead of parallel, although limit should not have
> affected this.

On what grounds do you assert that LIMIT can be parallelized?
AFAICS it has to be done by a single process to ensure that the
limit is enforced accurately.  So LIMIT below an aggregation
removes the opportunity to parallelize the aggregation.

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18330: The query planner chooses the wrong plan when using the parallel aggregation function
Next
From: Masahiko Sawada
Date:
Subject: Re: Potential data loss due to race condition during logical replication slot creation