On Thu, Jul 27, 2023 at 7:28 PM Ashutosh Bapat
wrote:
> The memory consumption is broken by the objects that consume memory
> during planning. The second attached patch is used to measure breakup
> by functionality . Here's a brief explanation of the rows in the
> table.
>
> 1. Restrictlist trans
Hi All,
When we implemented partitionwise join we disabled it by default (by
setting enable_partitionwise_join to false by default) since it
consumed a lot of memory and took a lot of time [1]. We also set
enable_partitionwise_aggregate to false by default since partitionwise
aggregates require pa
