pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: TB-sized databases
Date: Mon, 17 Mar 2008 19:47:12 -0400 (EDT)
Message-ID: <200803172347.m2HNlCD29489@momjian.us> (raw)
In-Reply-To: <10359.1197000850@sss.pgh.pa.us>


I have _not_ added a TODO for this item.  Let me know if one is needed.

---------------------------------------------------------------------------

Tom Lane wrote:
> Ron Mayer <rm_pg@cheapcomplexdevices.com> writes:
> > Tom Lane wrote:
> >> There's something fishy about this --- given that that plan has a lower
> >> cost estimate, it should've picked it without any artificial
> >> constraints.
> 
> > I think the reason it's not picking it was discussed back in this thread
> > too.
> > http://archives.postgresql.org/pgsql-performance/2005-03/msg00675.php
> > http://archives.postgresql.org/pgsql-performance/2005-03/msg00684.php
> > My offset 0 is forcing the outer join.
> > [Edit: Ugh - meant cartesian join - which helps this kind of query.]
> 
> Ah; I missed the fact that the two relations you want to join first
> don't have any connecting WHERE clause.
> 
> The concern I mentioned in the above thread was basically that I don't
> want the planner to go off chasing Cartesian join paths in general ---
> they're usually useless and would result in an exponential explosion
> in the number of join paths considered in many-table queries.
> 
> However, in this case the reason that the Cartesian join might be
> relevant is that both of them are needed in order to form an inner
> indexscan on the big table.  I wonder if we could drive consideration
> of the Cartesian join off of noticing that.  It'd take some rejiggering
> around best_inner_indexscan(), or somewhere in that general vicinity.
> 
> Way too late for 8.3, but something to think about for next time.
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
> 
>                 http://www.postgresql.org/about/donate

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (61+ messages)  latest in thread

Message-ID: <200803172347.m2HNlCD29489@momjian.us>
Permalink:  ../200803172347.m2HNlCD29489@momjian.us/
Also on:    postgresql.org/message-id/200803172347.m2HNlCD29489@momjian.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, rm_pg@cheapcomplexdevices.com
  Subject: Re: TB-sized databases
  In-Reply-To: <200803172347.m2HNlCD29489@momjian.us>
  References: <10359.1197000850@sss.pgh.pa.us> <200803172347.m2HNlCD29489@momjian.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