Re: Patch to clean Query after rewrite-and-analyze - reduces memusage up to 50% - increases TPS by up to 50%

2019-08-04 Thread Tom Lane
Daniel Migowski writes: > Am 03.08.2019 um 18:38 schrieb Tom Lane: >> (After thinking a bit, I'm guessing that it seemed not to break because >> your tests never actually exercised the generic-plan path, or perhaps >> there was always a plancache invalidation before we tried to use the >> query_li

Re: Patch to clean Query after rewrite-and-analyze - reduces memusage up to 50% - increases TPS by up to 50%

2019-08-03 Thread Daniel Migowski
Am 03.08.2019 um 18:38 schrieb Tom Lane: Daniel Migowski writes: While examining the reasons for excessive memory usage in prepared statements I noticed that RTE_JOIN-kind RTEs contain a bunch of columnNames and joinaliasvars, that are irrelevant after the Query after has been rewritten. Uh, t

Re: Patch to clean Query after rewrite-and-analyze - reduces memusage up to 50% - increases TPS by up to 50%

2019-08-03 Thread Tom Lane
Daniel Migowski writes: > While examining the reasons for excessive memory usage in prepared > statements I noticed that RTE_JOIN-kind RTEs contain a bunch of > columnNames and joinaliasvars, that are irrelevant after the Query after > has been rewritten. Uh, they're not irrelevant to planning

Patch to clean Query after rewrite-and-analyze - reduces memusage up to 50% - increases TPS by up to 50%

2019-08-03 Thread Daniel Migowski
Hello, While examining the reasons for excessive memory usage in prepared statements I noticed that RTE_JOIN-kind RTEs contain a bunch of columnNames and joinaliasvars, that are irrelevant after the Query after has been rewritten. I have some queries that join about 20 tables and select only