| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | Robert Treat <rob(at)xzilla(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Bruce Momjian <bruce(at)momjian(dot)us>, Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Should we update the random_page_cost default value? |
| Date: | 2025-10-08 04:02:39 |
| Message-ID: | CAApHDvpmpT575gSe2JZrKW-yTtQxza8x6FjFWhnpBEhSZUZmSQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 8 Oct 2025 at 08:15, Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:
> I've been doing this sort of thing for clients a long time, and I always test both directions when I come across a query that should be faster. For real-world queries, 99% of them have no change or improve with a lowered rpc, and 99% get worse via a raised rpc. So color me unconvinced.
I wonder how much past experience for this on versions before v18
count in now that we have AIO. The bar should have moved quite
significantly with v18 in terms of how often Seq Scans spend waiting
for IO vs Index Scans. So maybe Tomas's results shouldn't be too
surprising. Maybe the graph would look quite different with io_method
= 'sync'.. ?
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2025-10-08 04:10:03 | Re: sql/json query function JsonBehavior default expression's collation may differ from returning type's collation |
| Previous Message | Michael Paquier | 2025-10-08 03:54:18 | Re: Add stats_reset to pg_stat_all_tables|indexes and related views |