| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17059: postgresql 13 version problem related to query. |
| Date: | 2021-06-15 19:54:35 |
| Message-ID: | 439507.1623786875@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> út 15. 6. 2021 v 21:36 odesílatel Ram Pratap Maurya <
> ram(dot)maurya(at)lavainternational(dot)in> napsal:
>> Postgresql-12 :
>> -> Index Scan using retailer_code_12390127_idx
>> on tretailer_mst retailerlist (cost=0.42..5468.67 rows=146923 width=25)
>> (actual time=0.018..180.502 rows=144211 loops=1)
>>
>> Postgresql-13
>> -> Index Scan using
>> retailer_code_12390127_idx on tretailer_mst retailerlist (cost=0.38..0.59
>> rows=1 width=684) (actual time=0.028..928.347 rows=221068 loops=1)
There seem to be rather serious discrepancies between rowcount estimates
and reality on the v13 installation. Maybe an ANALYZE would help.
I'm also wondering why auto-analyze hasn't come along and improved
the situation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ram Pratap Maurya | 2021-06-15 20:00:43 | RE: BUG #17059: postgresql 13 version problem related to query. |
| Previous Message | Pavel Stehule | 2021-06-15 19:42:05 | Re: BUG #17059: postgresql 13 version problem related to query. |