From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ceri Storey <cez-misc.pgsql-perf@necrofish.org.uk>
Cc: Ceri Storey <cez@necrofish.org.uk>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Join optimisation Quandry
Date: Sun, 18 Jan 2004 21:21:00 -0500
Message-ID: <18213.1074478860@sss.pgh.pa.us> (raw)
In-Reply-To: <20040117115826.GD43530@mrtall.compsoc.man.ac.uk>
References: <20040114231014.GE53284@mrtall.compsoc.man.ac.uk>
<20040116094935.P66040@megazone.bigpanda.com>
<20040117010334.GA43530@mrtall.compsoc.man.ac.uk>
<20040117115826.GD43530@mrtall.compsoc.man.ac.uk>
Ceri Storey <cez-misc.pgsql-perf@necrofish.org.uk> writes:
> Although, as I've just found, another bottleneck is the title table.
> PostgreSQL seems to inst on doing a Seq Scan on the entire table.
> -> Seq Scan on tid (cost=0.00..20.00 rows=1000 width=8) (actual time=0.028..10.457 rows=17 loops=1)
It doesn't look like you've ever vacuumed or analyzed "tid" --- those
are the default cost and rows estimates. Although I'm unsure whether
the plan would change much if you had.
regards, tom lane
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, cez-misc.pgsql-perf@necrofish.org.uk, cez@necrofish.org.uk, sszabo@megazone.bigpanda.com
Subject: Re: Join optimisation Quandry
In-Reply-To: <18213.1074478860@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