Horton

Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10

Mukesh Chhatani <chhatani.mukesh@gmail.com>

View thread View on postgr.es
From: Mukesh Chhatani <chhatani.mukesh@gmail.com>
To: pgsql-bugs@postgresql.org
Date: 2019-11-13T18:37:30Z
Lists: pgsql-bugs, pgsql-hackers 
All,

Update I was able to resolve the problem by changing - partitioned tables to
single table and changing data type of 2 columns used in the joins from
varchar to varchar(50).

FYI.. default_statistics_target was set to 10000 but I changed it 100 and
even to 1000 and still planning time was high.

Still working on the dataset so that more people can investigate the issues.



--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html

Commits

  1. Include information on buffer usage during planning phase, in EXPLAIN output, take two.

  2. Include information on buffer usage during planning phase, in EXPLAIN output.

  3. Expose BufferUsageAccumDiff().