On Mon, 2021-03-15 at 10:53 -0600, S Bob wrote:
> We have a client that is running PostgreSQL 12, they have a table with
> 212 columns and 723 partitions
>
> It seems the planning time is consumed by generating 723 sub plans
>
> I suspect it's due to the fact that they are using hash based
> pa
On Mon, Mar 15, 2021 at 10:53:06AM -0600, S Bob wrote:
> We have a client that is running PostgreSQL 12, they have a table with 212
> columns and 723 partitions
>
> It seems the planning time is consumed by generating 723 sub plans
Is plannning time the issue ?
Please show diagnostic output. You
All;
We have a client that is running PostgreSQL 12, they have a table with
212 columns and 723 partitions
It seems the planning time is consumed by generating 723 sub plans
I suspect it's due to the fact that they are using hash based
partitioning, example:
CREATE TABLE rental_transact
On Fri, Mar 12, 2021 at 10:34 AM Thomas Munro wrote:
> It looks like your system is performing very badly for some other
> reason, so that synchronous I/O waits are only a small proportion of
> the time, and thus fsync=off doesn't speed things up very much. I'd
> look into profiling the system to
