Search Postgresql Archives

Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
From: Dimitrios Apostolou <jimis@xxxxxxx>
Date: Tue, 14 May 2024 18:14:45 +0200 (CEST)
Cc: pgsql-general@xxxxxxxxxxxxxxxxxxxx, David Rowley <dgrowleyml@xxxxxxxxx>
In-reply-to: <660a8477-4130-40da-3492-f8827c5c3596@gmx.net>
References: <7886a68f-b466-2131-1747-f69f0fb71a37@gmx.net> <69077f15-4125-2d63-733f-21ce6eac4f01@gmx.net> <559b0e40-63e6-fa9a-6b03-d1eba10f30f8@gmx.net> <1629463.1715372568@sss.pgh.pa.us> <660a8477-4130-40da-3492-f8827c5c3596@gmx.net>
Ui-outboundreport: notjunk:1;M01:P0:LoBn59Tg0YI=;jpuuIBuU3ocLgDeNGU/kcEng3sg SQL3ekVad6i6xjGjdeiS+va90eV5T3hdT8F5OkW7tcEKBfCiE313I3EBEkUOSLSr5127ND4YN 5bSYiw2vfC3gfQUqyFr2/QUKMkqUaTpvrqEioTaBgwb9JczAtqT7Yw8RMYt/agTj0rjk8W1aQ tURnReVI1Zh8xpODJf2xjTplgzPzxDU/e+7ih6AGDCo+3KlRboM4VoEbBShEvFGEbwlXPYRyv bk04klNGjyV/K+G9R2SjCTXD7wawznlnR6+ivaYuNVjWuCHMl0ZKpukZuhaGeKarOz2m3ifBD bHF1t8Scvhz2lUB95vCtt7SjlDmR5yT2/Y0c66Fy2+qC5bkfS2J69OSkfYZd4YA7tuHQ1vVsW kHIzCqfis7QFCOkQZw8PkMgMKU3rhAR+YbEymrLHi+0swfvvGBHH7IN9kx17+p+uUUTGxgd/m R3z6ODWKiHGpjd3eoBqCwgo4eb70saTa1Mb1cPRiak7AUKQ7luq8TDYMsnumRgJ65/yeCShtI DsYPOQhpQg5JpacB12iNvZK6SE1L51tXT9nPbG+AMQ7T9isPBzvXBNIxqrSWcC1AHvRIO+iJR MqmKrqIJiljBJJUWMMsc+AOaiJTodu6UmSTlIoyonUmiD5kTy3EzP0cl6i5YyJ9VFeHRsd87P Zx0LLT5++Vpl6WDU4U86fQx8Iim1TnXcMq2DVO38z3b2Lu2kg50fyWYEfunpR9vRkqgap1Tei XFwWv4DRLVEmFYXTDenViccrpGw/JTDj3F0axT784B8aD1FKkhSBnoVWNo/ZtzQbc+A8xg9/e jTkVGC+/8epeA6+3Ege067lVXdpDEsweEuRAbmf7OdRl0=

On Tue, 14 May 2024, Dimitrios Apostolou wrote:


It took long but if finished:

ANALYZE
Time: 19177398.025 ms (05:19:37.398)


I see now that default_statistics_target is globally set to 500, so this
is probably the reason it took so long. I guess with the default of 100,
it would take approximately one hour. This is much better to have in a
cron job. :-)

Dimitris

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
  - From: Dimitrios Apostolou
- Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
  - From: Dimitrios Apostolou
- Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
  - From: Dimitrios Apostolou
- Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
  - From: Tom Lane
- Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
  - From: Dimitrios Apostolou

Prev by Date: Re: Valid until
Next by Date: Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
Previous by thread: Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
Next by thread: Unnecessary buffer usage with multicolumn index, row comparison, and equility constraint
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]