Re: BUG #17059: postgresql 13 version problem related to query.
От | Tom Lane |
---|---|
Тема | Re: BUG #17059: postgresql 13 version problem related to query. |
Дата | |
Msg-id | 439507.1623786875@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #17059: postgresql 13 version problem related to query. (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
RE: BUG #17059: postgresql 13 version problem related to query.
|
Список | pgsql-bugs |
Pavel Stehule <pavel.stehule@gmail.com> writes: > út 15. 6. 2021 v 21:36 odesílatel Ram Pratap Maurya < > ram.maurya@lavainternational.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
В списке pgsql-bugs по дате отправления: