From: | Michael Kemanetzis <michael(dot)kemanetzis(at)gmail(dot)com> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Select query ignores index on large table |
Date: | 2011-01-28 12:57:45 |
Message-ID: | AANLkTikuWEP0iD2gB6e0HosRO9wwnLQpb3pigSr9ocrM@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks, it did help. Now queries run in zero time.
I had thought of doing that....but since the same configuration was working
ok on MSSQL I thought it should also here.
Now with that index the server query times are a lot faster than MSSQL
without it.
Since it is working I will leave it like that. At least till I know more on
how postgre behaves (and databases in general) with indexes.
Thanks again!
On Thu, Jan 27, 2011 at 4:12 PM, hubert depesz lubaczewski <
depesz(at)depesz(dot)com> wrote:
> On Thu, Jan 27, 2011 at 04:04:02PM +0200, Michael Kemanetzis wrote:
> > Hello, I'm experiencing a strange behavior running a simple select query
> on
> > a table that has about 12 million rows. Specifically, changing the
> "LIMIT"
> > value seems to change the execution plan but the result in one of the
> cases
> > is unjustifiably slow, as if it ignores all indexes.
> >
> > The table structure, the queries used and the results are here:
> > http://pastebin.com/fn36BuKs
> >
> > Is there anything I can do to improve the speed of this query?
>
> create index qq on vehicleevent (veh_id, event_id)
> could help.
>
> Best regards,
>
> depesz
>
> --
> Linkedin: http://www.linkedin.com/in/depesz / blog:
> http://www.depesz.com/
> jid/gtalk <http://www.depesz.com/%0Ajid/gtalk>: depesz(at)depesz(dot)com /
> aim:depeszhdl / skype:depesz_hdl / gg:6749007
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Kemanetzis | 2011-01-28 13:22:34 | Re: Select query ignores index on large table |
Previous Message | Girts Laudaks | 2011-01-28 12:54:18 | Re: Dumpall without OID |