Re: Query taking too long. Problem reading explain output. - Mailing list pgsql-performance

From Tom Lane
Subject Re: Query taking too long. Problem reading explain output.
Date
Msg-id 15793.1191420918@sss.pgh.pa.us
Whole thread Raw
In response to Query taking too long. Problem reading explain output.  (Henrik <henke@mac.se>)
Responses Re: Query taking too long. Problem reading explain output.
List pgsql-performance
Henrik <henke@mac.se> writes:
> Here is the query if needed.
> explain analyze SELECT file_name FROM tbl_file_structure JOIN
> tbl_file ON pk_file_id = fk_file_id JOIN tbl_structure ON
> pk_structure_id = fk_structure_id JOIN tbl_archive ON pk_archive_id
> =fk_archive_id JOIN tbl_share ON pk_share_id =fk_share_id JOIN
> tbl_computer ON pk_computer_id = fk_computer_id JOIN tbl_filetype ON
> pk_filetype_id = fk_filetype_id LEFT OUTER JOIN tbl_job ON
> tbl_archive.fk_job_id = pk_job_id LEFT OUTER JOIN tbl_job_group ON
> tbl_job.fk_job_group_id = pk_job_group_id WHERE LOWER(file_name) LIKE
> LOWER('index.php%') AND (computer_name = 'SOLARIS2') AND
> (fk_archive_id = 56) AND archive_complete = true  AND (job_group_type
> = 'B' OR job_group_type IS NULL) GROUP BY file_name, file_ctime,
> structure_path, pk_computer_id, filetype_icon, computer_name,
> share_name, share_path;

[ counts the JOINs... ]  Try raising join_collapse_limit.  I think the
planner may be neglecting to consider the join order you need.

            regards, tom lane

pgsql-performance by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Query taking too long. Problem reading explain output.
Next
From: "Sabin Coanda"
Date:
Subject: can't shrink relation