| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Tim Uckun <timuckun(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres seems to use indexes in the wrong order |
| Date: | 2015-01-24 00:25:57 |
| Message-ID: | 54C2E695.1020703@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/22/2015 11:04 PM, Tim Uckun wrote:
> Take a look at this explain
>
> http://explain.depesz.com/s/TTRN
I maybe missing it, but I do not see the actual query.
>
> The final number of records is very small but PG is starting out with a
> massive number of records and then filtering most of them out.
>
> I don't want to really force pg to always use the same index because in
> some cases this strategy would win but I am wondering if there is
> anything I need to do in order to get the planner to make better decisions.
>
> I already did an analyze on the table.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G Johnston | 2015-01-24 01:18:47 | Re: CLOG read problem after pg_basebackup |
| Previous Message | Al Eridani | 2015-01-23 23:43:07 | Re: PostgreSQL server does not notice that clients have disappeared |