Re: Unexpected Performance for the Function simplify_function

From: Ba Jinsheng <bajinsheng(at)u(dot)nus(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Unexpected Performance for the Function simplify_function
Date: 2024-10-25 09:29:15
Message-ID: SEZPR06MB6494C2E2D24798C7A66F4D3D8A4F2@SEZPR06MB6494.apcprd06.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>It looks like the better plan involves a
>nestloop with inner indexscan on lineitem, which is something whose
>estimated cost depends enormously on random_page_cost. You've given
>us exactly zero detail about your test conditions, so it's hard to say
>more than that.

I used the default configuration in the file src/backend/utils/misc/postgresql.conf.sample
So the random_page_cost = 4.0

Best regards,

Jinsheng Ba

Notice: This email is generated from the account of an NUS alumnus. Contents, views, and opinions therein are solely those of the sender.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andrei Lepikhov 2024-10-25 09:38:24 Re: Unexpected Performance for the Function simplify_function
Previous Message Ba Jinsheng 2024-10-25 09:26:17 Re: Unexpected Performance for the Function simplify_function