6 aug 2007 kl. 21:47 skrev Heikki Linnakangas:
Henrik Zagerholm wrote:
I know the query retrieves way more which is really necessary to
show to
the user so I would gladly come up with a way to limit the query
so the
GUI doesn't hang for several minutes if a user does a bad search.
The prob
Henrik Zagerholm wrote:
> I know the query retrieves way more which is really necessary to show to
> the user so I would gladly come up with a way to limit the query so the
> GUI doesn't hang for several minutes if a user does a bad search.
> The problem is that I don't know a good way of limit the
6 aug 2007 kl. 16:58 skrev Tom Lane:
Henrik Zagerholm <[EMAIL PROTECTED]> writes:
... 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
Henrik Zagerholm <[EMAIL PROTECTED]> writes:
> ... 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_shar
Hello list,
We have a database keeping track of old files on different computers.
We have now added some search functionality to this system.
The problem is that on some searches it is really really slow and the
problem lies in the planner are using seq scans on tables with over
20 million ro
