Tom Lane schrieb am 27.05.2016 um 15:48:
Thomas Kellerer writes:
while playing around with the parallel aggregates and seq scan in
9.6beta I noticed that Postgres will stop using parallel plans when
cpu_tuple_cost is set to a very small number.
If you don't reduce the parallel-plan cost facto
Thomas Kellerer writes:
> while playing around with the parallel aggregates and seq scan in 9.6beta I
> noticed that Postgres will stop using parallel plans when cpu_tuple_cost is
> set to a very small number.
If you don't reduce the parallel-plan cost factors proportionally,
it's not very surp
On Fri, 27 May 2016, 9:26 p.m. Thomas Kellerer, wrote:
> Hello,
>
> while playing around with the parallel aggregates and seq scan in 9.6beta
> I noticed that Postgres will stop using parallel plans when cpu_tuple_cost
> is set to a very small number.
>
> When using the defaults and max_parallel_
