Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: nickr(at)mirth(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index
Date: 2014-04-30 23:22:19
Message-ID: 9896.1398900139@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

nickr(at)mirth(dot)com writes:
> It would appear that when you order on a column such that the query plan
> scans across a composite, multi-type index (say, bigint and integer), and
> the plan runs through an Index Cond, doing all that AND a LIMIT clause no
> longer works. And by "no longer works" I mean the query does not return any
> results when it should.

I failed to reproduce any such problem in a little bit of trying. Can you
create a self-contained test case?

The symptoms seem consistent with the theory that that index is corrupt
... have you tried REINDEXing it?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nick Rupley 2014-04-30 23:39:14 Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index
Previous Message nickr 2014-04-30 21:40:55 BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index