RE: [EXT] Re: Query runtime differences- trying to understand why. - Mailing list pgsql-general

From Dirschel, Steve
Subject RE: [EXT] Re: Query runtime differences- trying to understand why.
Date
Msg-id DM6PR03MB43326A344E6B3E4FF5AFF35EFA83A@DM6PR03MB4332.namprd03.prod.outlook.com
Whole thread Raw
In response to Re: Query runtime differences- trying to understand why.  (Andreas Kretschmer <andreas@a-kretschmer.de>)
List pgsql-general
Sorry.  DB is Aurora Postgres 14.6.  Hints are enabled via extension pg_hint_plan.  But my question isn't so much about
thehints but the execution plan and where the time is going and why it appears for 1 execution of the query skipping
lockedrows seems to take a lot more time than another execution of the query.
 

Regards

-----Original Message-----
From: Andreas Kretschmer <andreas@a-kretschmer.de> 
Sent: Wednesday, November 29, 2023 3:10 PM
To: pgsql-general@lists.postgresql.org
Subject: [EXT] Re: Query runtime differences- trying to understand why.

External Email: Use caution with links and attachments.



Am 29.11.23 um 21:25 schrieb Dirschel, Steve:
>
> I have a question on the execution time of a query and the 
> fluctuations I'm seeing.  I enabled auto_trace to capture some actual 
> executions of a query by an app.  Below are 2 executions of it.  The 
> top one took 1.697 milliseconds. The 2nd one took 31.241 milliseconds.  
> Note the query has hints in it
>

what database are you using? PostgreSQL doesn't hav hints...

Regards, Andreas

--
Andreas Kretschmer - currently still (garden leave) Technical Account Manager (TAM)
https://urldefense.com/v3/__http://www.enterprisedb.com__;!!GFN0sa3rsbfR8OLyAw!eF3r308h3pnOusNslRf-zZZ1LUoQFkGOKK47Sm1ByfdIdLAtF0xPY4-4Xuo_F25zoV12fGtyNUelCdG10fZEKldOigKm0FXp$





pgsql-general by date:

Previous
From: Andreas Kretschmer
Date:
Subject: Re: Query runtime differences- trying to understand why.
Next
From: H
Date:
Subject: Re: Installing extension temporal_tables for PG13