pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Miroslav Šulc <miroslav.sulc@startnet.cz>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-performance@postgreSQL.org
Subject: Re: Avoiding tuple construction/deconstruction during joining
Date: Mon, 14 Mar 2005 14:22:35 -0500
Message-ID: <29030.1110828155@sss.pgh.pa.us> (raw)
In-Reply-To: <4235E1EF.2000402@startnet.cz>
References: <42345D24.8070104@startnet.cz>
	<14577.1110821062@sss.pgh.pa.us>
	<4235E1EF.2000402@startnet.cz>

=?windows-1250?Q?Miroslav_=8Aulc?= <miroslav.sulc@startnet.cz> writes:
> seriously, I am far below this level of knowledge. But I can contribute 
> a test that (maybe) can help. I have rewritten the query so it JOINs the 
> varchar() fields (in fact all fields except the IDPK) at the last INNER 
> JOIN. Though there is one more JOIN, the query is more than 5 times 
> faster (1975.312 ms) :-)

That confirms my thought that passing the data up through multiple
levels of join is what's killing us.  I'll work on a solution.  This
will of course be even less back-patchable to 8.0.* than Ogawa's work,
but hopefully it will fix the issue for 8.1.

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <29030.1110828155@sss.pgh.pa.us>
Permalink:  ../29030.1110828155@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29030.1110828155@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, miroslav.sulc@startnet.cz, pgsql-hackers@postgreSQL.org
  Subject: Re: Avoiding tuple construction/deconstruction during joining
  In-Reply-To: <29030.1110828155@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