Re: Problem with inherited tables vs query planning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave Golombek" <daveg(at)blackducksoftware(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with inherited tables vs query planning
Date: 2007-05-18 15:29:09
Message-ID: 28272.1179502149@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Dave Golombek" <daveg(at)blackducksoftware(dot)com> writes:
> Ah, I forgot to try the index on the base table using 8.2, which does indeed
> solve the problem. It unfortunately doesn't help with 8.1.4, which we have
> in the field; any thoughts on workarounds for older versions or should I
> just use a function until we can upgrade everywhere? We have 150 million
> rows spread across 16 child tables, which should help cost estimation.

Sorry, 8.1 is just not capable of generating that type of plan --- it
won't push join clauses down into an Append.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2007-05-18 15:35:17 Re: Large Database Restore
Previous Message Tom Lane 2007-05-18 15:14:59 Re: Location of \pgsql\src\test\regress\readme.