From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "hehaochen(at)hotmail(dot)com" <hehaochen(at)hotmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: change the default value of enable_bitmapscan to off |
Date: | 2023-01-14 15:57:07 |
Message-ID: | 1005543.1673711827@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"hehaochen(at)hotmail(dot)com" <hehaochen(at)hotmail(dot)com> writes:
> The default is enable_bitmapscan on. However, TPC-H.query17 get slower running on my NVMe SSD (WD SN850) after switching on the parameter: latency drop from 9secs to 16secs. During a B-tree Index Scan, bitmapscan optimization converts random I/O into sequential. However, many users use SSDs rather than HDDs. But they may not know the trick. Is there a possibility that can change the default value to off?
Use ALTER SYSTEM SET, or edit postgresql.conf:
https://www.postgresql.org/docs/current/config-setting.html
Note that changing planner parameters on the basis of a single
query getting slower is a classic beginner error. You need
to think about the totality of the installation's workload.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | aditya desai | 2023-01-19 17:30:41 | ALTER STATEMENT getting blocked |
Previous Message | Pavel Stehule | 2023-01-14 15:00:29 | Re: change the default value of enable_bitmapscan to off |