Thank you for your post. I finally spent some quality time with the query
planner section in the docs' server config chapter. Very instructive, even
considering that most of it went over my head!
On Sat, Mar 8, 2008 at 4:08 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
...have you got effective_cache
Kynn Jones wrote:
my_db=> SET ENABLE_SEQSCAN TO OFF;
my_db=> EXPLAIN ANALYZE SELECT * FROM T NATURAL JOIN B;
QUERY PLAN
---
"Kynn Jones" <[EMAIL PROTECTED]> writes:
> So it seems like turning off ENABLE_SEQSCAN is the way to go.
Try reducing random_page_cost a bit instead. Also, have you got
effective_cache_size set to something that's realistic for your
machine?
One problem with this test is that your smaller tables
On Sat, Mar 8, 2008 at 1:01 PM, Heikki Linnakangas <[EMAIL PROTECTED]>
wrote:
> Kynn Jones wrote:
> > Hi!
> >
> > As part of a data warehousing project, I need to pre-process data
> downloaded
> > from an external source, in the form of several large flat files. This
> > preprocessing entails che
Kynn Jones wrote:
Hi!
As part of a data warehousing project, I need to pre-process data downloaded
from an external source, in the form of several large flat files. This
preprocessing entails checking the validity of various data items, and
discarding those that fail to pass all the checks.
Cu
