Message-ID: <4B8AF25C.3030209@agliodbs.com>
Date: Sun, 28 Feb 2010 14:46:52 -0800
From: Josh Berkus <josh@agliodbs.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: Kenneth Marshall <ktm@rice.edu>
CC: Kevin Kempter <kevink@consistentstate.com>,
	pgsql-performance@postgresql.org
Subject: Re: partitioned tables query not using indexes
References: <201002240736.36341.kevink@consistentstate.com>
	<4B8AD21A.2020904@agliodbs.com>
	<20100228215157.GA14613@it.is.rice.edu>
In-Reply-To: <20100228215157.GA14613@it.is.rice.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 2/28/10 1:51 PM, Kenneth Marshall wrote:
> On Sun, Feb 28, 2010 at 12:29:14PM -0800, Josh Berkus wrote:
>>> However the same query against the base table when specifying the check 
>>> constraint key in the where clause produces sequential scans:
>> Does the "master" table have the same indexes as the slave partitions?
>>
>> --Josh Berkus
>>
> Does this help? I have an empty base table without indexes and partitions
> underneath that do have the index. I did not think that an index on the
> parent table did anything.

I'm not sure that it does, but "try it and see" is easier than reading
the planner code.

--Josh Berkus