pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kynn Jones <kynnjo@gmail.com>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Joins and DELETE FROM
Date: Sat, 08 Mar 2008 15:08:46 -0500
Message-ID: <6359.1205006926@sss.pgh.pa.us> (raw)
In-Reply-To: <c2350ba40803081102v14d7c3f0u349fb361351fec5a@mail.gmail.com>
References: <c2350ba40803080931y363d6fd9oaaca11a0ea4f1b79@mail.gmail.com>
	<47D2D485.9040103@enterprisedb.com>
	<c2350ba40803081102v14d7c3f0u349fb361351fec5a@mail.gmail.com>

"Kynn Jones" <kynnjo@gmail.com> 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 probably fit in
memory whereas the big ones may not, so it's not a given that your test
accurately reflects how the real query will go down.

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <6359.1205006926@sss.pgh.pa.us>
Permalink:  ../6359.1205006926@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6359.1205006926@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, kynnjo@gmail.com, heikki@enterprisedb.com
  Subject: Re: Joins and DELETE FROM
  In-Reply-To: <6359.1205006926@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox