Hello Gregory,
On 10/3/07, Greg Williamson [EMAIL PROTECTED] wrote:
Giulio Cesare Solaroli wrote:
Hello everybody,
I have just joined the list, as I am experiencing a degradation on
performances on my PostgreSQL instance, and I was looking for some
insights on how to fix/avoid it.
Hello,
thanks to the added info available running the explain plan through
pgsl (instead of using pgAdmin) I was able to realize that an
(implicitly created) trigger was the culprit of the slowdown I was
suffering.
Adding an index on the foreign key the trigger was monitoring solved the issue.
Hello list,
I have a little query that takes too long and what I can see in the
explain output is a seq scan on my biggest table
( tbl_file_structure) which I can't explain why.
Here is the output. I hope this is formatted correctly. If not, let
me know and I'll paste it somewhere.
On Wed, Oct 03, 2007 at 10:03:53AM +0200, Henrik wrote:
I have a little query that takes too long and what I can see in the
explain output is a seq scan on my biggest table ( tbl_file_structure)
which I can't explain why.
Here's where almost all of the time is taken:
Hash Join
Henrik [EMAIL PROTECTED] 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
