Re: Join optimization for inheritance tables

From: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
To: Herodotos Herodotou <Herodotos(dot)Herodotou(at)asterdata(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Eric Friedman <Eric(dot)Friedman(at)asterdata(dot)com>, John Cieslewicz <John(dot)Cieslewicz(at)asterdata(dot)com>, Dheeraj Pandey <Dheeraj(dot)Pandey(at)asterdata(dot)com>, "hero(at)cs(dot)duke(dot)edu" <hero(at)cs(dot)duke(dot)edu>, "nedyalko(at)cs(dot)duke(dot)edu" <nedyalko(at)cs(dot)duke(dot)edu>
Subject: Re: Join optimization for inheritance tables
Date: 2009-08-10 23:41:38
Message-ID: 4A80B032.6030604@timbira.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Herodotos Herodotou escreveu:
> This patch extends the query optimizer to consider joins between child tables when hierarchies are joined together.
>
> Short description: when the optimizer considers join paths between two tables with child tables, it only creates join paths over two append paths. In this patch we extend the optimizer to consider joins between the child tables from the two parent relations, based on the child table constraints. The idea is that only child tables with overlapping constraints need to be joined, and not the entire hierarchies with each other. This optimization can provide significant benefits in terms of execution time. A short motivation example as well as the overall algorithm description could be found in the attached presentation.
>
I added it to the next commitfest [1].

[1] https://commitfest.postgresql.org/action/commitfest_view?id=3

--
Euler Taveira de Oliveira
http://www.timbira.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-10 23:57:10 Re: machine-readable explain output v4
Previous Message Bruce Momjian 2009-08-10 23:22:44 Re: hot standby - merged up to CVS HEAD