Home > database >  Postgresql execution plan, slow statement for bosses to give directions. Thanks
Postgresql execution plan, slow statement for bosses to give directions. Thanks

Time:09-18


Is I the main table link table 2 is the primary key table 1 didn't go index table 3 is a composite index, index but didn't go? Strange arguably data quantity also many actuators should go index have bosses give directions of gratitude

CodePudding user response:

Postgresql, sometimes may be associated and collecting information is incorrect, analyze if this is available to collect the
If not, the execution of this statement, before the set enable_seqscan=off, after execution, the set again enable_seqscan=on

CodePudding user response:

reference 1st floor trainee response:
postgresql, sometimes may be associated and collection of information is wrong, if so, can analyze to collect the
If not, the execution of this statement, before the set enable_seqscan=off, performed, and then restore the set enable_seqscan=on





Is walked index. But is the filter conditions, but not join condition index, dictionary tables that did go index
  • Related