Skip site navigation (1) Skip section navigation (2)

TODO idea - implicit constraints across child tables with a common column as primary key (but obviously not a shared index)

From: Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: TODO idea - implicit constraints across child tables with a common column as primary key (but obviously not a shared index)
Date: 2007-04-23 18:10:29
Message-ID: 1177351829.766323.69790@p77g2000hsh.googlegroups.com (view raw or flat)
Thread:
Lists: pgsql-hackers
If you have a table with a bunch of children, and these children all
have a primary key which is generated from the same sequence, assuming
that you're partitioning based on date (ie, this is a transaction
record table), it would be nice if the planner could spot that all
tables have a primary key on a column used as a join condition, check
the min / max to see if there is overlap between tables, then apply
CBE as if constraints existed.

This strikes me as a pretty common situation, certainly we're seeing
it here.

Andrew


Responses

pgsql-hackers by date

Next:From: Gregory StarkDate: 2007-04-23 18:46:52
Subject: Re: TODO idea - implicit constraints across child tables with a common column as primary key (but obviously not a shared index)
Previous:From: Dorochevsky,MichelDate: 2007-04-23 17:28:22
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b ject

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group