Stefan Keller <sfkel...@gmail.com> wrote: > Finally, setting random_page_cost to 1 helps also - but I don't > like this setting neither.
Well, you should learn to like whichever settings best model your actual costs given your level of caching and your workload. ;-) FWIW, I have found page costs less volatile and easier to tune with cpu_tuple_cost increased. I just always start by bumping that to 0.03. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
