From: | John Cheng <jlcheng(at)ymail(dot)com> |
---|---|
To: | nha <lyondif02(at)free(dot)fr> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem search on text arrays, using the overlaps (&&) operator |
Date: | 2009-07-23 04:49:42 |
Message-ID: | 99603.64501.qm@web43410.mail.sp1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- "nha" <lyondif02(at)free(dot)fr> wrote:
>
> Another way could concern the hash join. It has been shown that this
> step costs a lot with respect to the overall runtime. Depending on
> available storage space and DBMS load, a kind of materialized view
> may
> be handled in order to cut off the overloading join. Here are some
> suggested statements to create this helper table:
>
[snip]
Hi nha,
Sorry about the long lag after your last post. I didn't want to post
back until I had something solid to report on. Using a materialized
view turned out to be the best way to solve my problem. My coworker
designed a new table that consists of the key columns for 3 large
tables that were being joined. A trigger is used to make sure
the "materialized view" is kept up-to-date. Since new data is added
infrequently (once a month), the cost of keeping the materialized view
up-to-date is cheap. The resulting query runs exceedingly fast! :)
Thank you so much for your guidance. I have learned a lot from this
incident!
From | Date | Subject | |
---|---|---|---|
Next Message | Steffen Kuhn | 2009-07-23 06:45:38 | Re: 8.4.0 installer for Windows from EnterpriseDB does not seem to include pgagent |
Previous Message | Jeff Davis | 2009-07-23 00:40:32 | Re: Help using SELECT INTO to make schema |