Re: Query taking too long. Problem reading explain output.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Henrik <henke(at)mac(dot)se>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Query taking too long. Problem reading explain output.
Date: 2007-10-03 14:15:18
Message-ID: 15793.1191420918@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Henrik <henke(at)mac(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Sabin Coanda 2007-10-04 09:43:12 can't shrink relation
Previous Message Michael Fuhr 2007-10-03 13:31:29 Re: Query taking too long. Problem reading explain output.