From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | marko(at)joh(dot)to |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #11500: PRIMARY KEY index not being used |
Date: | 2014-09-26 17:44:39 |
Message-ID: | 8043.1411753479@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
marko(at)joh(dot)to writes:
> PostgreSQL version: 9.1.12
> We've been observing a performance problem where a PRIMARY KEY index is not
> being used. The problem looks like this:
In 9.2 and again in 9.3, we significantly changed the planner's modeling
of index access costs, with a view towards making better choices when
there are multiple plausible indexes to use. If you can reproduce this
misbehavior in 9.3 or later it would be worth looking into; but we're not
going to change 9.1's estimation rules at this late date. People running
on back branches tend to want plan stability in my experience.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | orasnita | 2014-09-27 20:07:38 | BUG #11501: PostgreSQL for Windows (installer) cannot be installed by screen reader users (blind computer users) |
Previous Message | Tom Lane | 2014-09-26 16:57:18 | Re: BUG #11457: The below query crashes 9.3.5, but not 9.3.4 |