Re: Significant Execution Time Difference Between PG13.14 and PG16.4 for Query on information_schema Tables.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, nikhil raj <nikhilraj474(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Significant Execution Time Difference Between PG13.14 and PG16.4 for Query on information_schema Tables.
Date: 2024-08-29 20:53:03
Message-ID: 295441.1724964783@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> On Thu, Aug 29, 2024 at 4:47 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> In the meantime, I think this test case is mighty artificial,
>> and it wouldn't bother me any to just take it out again for the
>> time being.

> Yeah, I think we can remove the 't1.two+t2.two' test case if we go
> with your proposed patch to address this performance regression.

Here's a polished-up patchset for that. I made the memoize test
removal a separate patch because (a) it only applies to master
and (b) it seems worth calling out as something we might be able
to revert later.

I found one bug in the draft patch: add_nulling_relids only processes
Vars of level zero, so we have to apply it before not after adjusting
the Vars' levelsup. An alternative could be to add a levelsup
parameter to add_nulling_relids, but that seemed like unnecessary
complication.

regards, tom lane

Attachment Content-Type Size
v1-0001-Remove-one-memoize-test-case-added-by-commit-069d.patch text/x-diff 4.0 KB
v1-0002-Avoid-inserting-PlaceHolderVars-in-cases-where-pr.patch text/x-diff 9.0 KB

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rumpi Gravenstein 2024-08-29 23:18:16 Analytic Function Bug
Previous Message Ron Johnson 2024-08-29 18:10:45 Re: PgBackRest Full backup and N/W reliability

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-08-29 20:54:15 Re: pl/pgperl Patch for adding $_FN detail just like triggers have for $_TD
Previous Message Masahiko Sawada 2024-08-29 20:48:53 Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation