BUG #16377: select stuck when use order by and limit 1 if order-by-field has one index and result has no records

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: kingyzf(at)outlook(dot)com
Subject: BUG #16377: select stuck when use order by and limit 1 if order-by-field has one index and result has no records
Date: 2020-04-18 10:04:05
Message-ID: 16377-86af0a40aa096b0d@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16377
Logged by: Yunfeng Wang
Email address: kingyzf(at)outlook(dot)com
PostgreSQL version: 11.6
Operating system: Centos 7.6
Description:

select stuck when use order by and limit 1 if order-by-field has one
index:
and possibility is high if result has no records, otherwise possibility is
low;
if no "limit 1" or no index on column pay_date, no problem;

sql:
select * from
(select ( case when pre_pay is null then 0 else pre_pay end ) as "PRE_PAY"

from inpatientprepay
where cancel='0'
and ehrid=4
order by pay_date desc
) as t
limit 1
;
other info: the inpatientprepay table has nine million records, I think
it's stuck because if no limit 1 ,speed is ok;

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2020-04-18 13:36:17 Re: BUG #16377: select stuck when use order by and limit 1 if order-by-field has one index and result has no records
Previous Message Michael Paquier 2020-04-18 09:28:56 Re: BUG #16369: Segmentation Faults and Data Corruption with Generated Columns