1
someone knows some tool that assists in adjusting the parameters of the postgresql.conf file.
I’ve used the PGTUNE and of Pgconfig, but they indicate nothing of the parameters:
- cpu_tuple_cost
- cpu_index_tuple_cost
- cpu_operator_cost
- seq_page_cost
- random_page_cost
I’m with the problem reported in the other post: Why cost estimates in Postgresql are so wrong?, in which the optimizer is always choosing to do full-scan instead of strategies indexed for example. I understand that sometimes it really is more agile to do full-scan than to go out running an index, which requires random access, but I also tested with Ssds disks, changing random_page_cost = 1, and continued the problem (incorrect cost) and indexed strategies, are less efficient than without indices. I think I should adjust these better settings. If you have any tool tips or other form, please return.