Les plans d'exécution sont historisés

Désolé J-F tu avais raison :

 

select SQL_ID,COST,TIME from DBA_HIST_SQL_PLAN

Stop arnaque

Arnaque aux dentistes mais pas que!

Cette recette c'est pour toi mon BB d'amour

Les Beignets de Carnaval !

Tuning Latch Contention: Cache-Buffers-Chain Latches

Researching Further

Re-querying v$session_wait, I see that a couple of latches are hot. I will consider one latch children with latch address 19875043200 as an example, and drill down further.

 

Hang Those Buffers!

Next, I needed to find buffers protected by these latch children, and then find the buffers causing latch contention. Many such hash buckets (and so, numerous buffers) are protected by a latch children. 

I don’t favour the above script, since its performance is not optimal. It is much easier to dump the blocks and convert them to object ids. Let’s dump these three blocks.

Now I can query dba_objects to find the object_names.

https://blog.pythian.com/tuning-latch-contention-cache-buffers-chain-latches/

[PostgreSQL] Identifying locked objects

my client called me. Help I m doing big insert on partitionned tables and it s running very low.

Beside that the statement is faster during the midnight.