pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthew <matthew@flymine.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: TB-sized databases
Date: Thu, 06 Dec 2007 20:55:02 -0500
Message-ID: <6126.1196992502@sss.pgh.pa.us> (raw)
In-Reply-To: <17456.1196963738@sss.pgh.pa.us>
References: <4544e0330711260904g45d893a8ub1731e245aa8fc84@mail.gmail.com>
	<13851.1196351131@sss.pgh.pa.us>
	<1196352866.4246.1304.camel@ebony.site>
	<200712051507.22745.xzilla@users.sourceforge.net>
	<1196933896.4255.340.camel@ebony.site>
	<20071206154212.GP5294@mathom.us>
	<15753.1196957598@sss.pgh.pa.us>
	<Pine.LNX.4.58.0712061626370.3731@aragorn.flymine.org>
	<17456.1196963738@sss.pgh.pa.us>

I wrote:
> Hmm.  IIRC, there are smarts in there about whether a mergejoin can
> terminate early because of disparate ranges of the two join variables.
> Seems like it should be straightforward to fix it to also consider
> whether the time-to-return-first-row will be bloated because of
> disparate ranges.

I've posted a proposed patch for this:
http://archives.postgresql.org/pgsql-patches/2007-12/msg00025.php

			regards, tom lane



view thread (61+ messages)  latest in thread

Message-ID: <6126.1196992502@sss.pgh.pa.us>
Permalink:  ../6126.1196992502@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6126.1196992502@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, matthew@flymine.org
  Subject: Re: TB-sized databases
  In-Reply-To: <6126.1196992502@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