| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org>, Jaume Sabater <jsabater(at)gmail(dot)com>, Sergio Chavarria <sergio(dot)chavarria(at)gmail(dot)com> |
| Subject: | Re: Strange behaviour with a query |
| Date: | 2009-04-17 10:30:19 |
| Message-ID: | dcc563d10904170330t5bd8accdva0b4b77bca4286d1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, Apr 17, 2009 at 4:29 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Fri, Apr 17, 2009 at 4:17 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>> On Fri, Apr 17, 2009 at 3:00 AM, Iñigo Martinez Lasala
>> <imartinez(at)vectorsf(dot)com> wrote:
>>> Hi everybody again.
>>>
>>> Deleting rel_dis_can_fk index has solved the problem! But.... why??
>>
>> Hard to say without explain analyze output.
>>
>
> I'd hazard a guess that you're getting a lot more rows back from the
> bitmap scan of rel_dis_can_fk than the query planner expects. But
> that's just a guess.
Try craniking up your default stats setting and running analyze again
and seeing if it runs fast even with the index.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Iñigo Martinez Lasala | 2009-04-17 11:58:35 | Re: Strange behaviour with a query |
| Previous Message | Scott Marlowe | 2009-04-17 10:29:29 | Re: Strange behaviour with a query |