| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Kenneth Marshall <ktm(at)rice(dot)edu> |
| Cc: | Kevin Kempter <kevink(at)consistentstate(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: partitioned tables query not using indexes |
| Date: | 2010-02-28 22:46:52 |
| Message-ID: | 4B8AF25C.3030209@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris | 2010-03-01 02:38:08 | Re: [HACKERS] full text search index scan query plan changed in 8.4.2? |
| Previous Message | Josh Berkus | 2010-02-28 22:41:46 | Re: [HACKERS] full text search index scan query plan changed in 8.4.2? |