Re: Speedup truncations of temporary relation forks

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniil Davydov <3danissimo(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Speedup truncations of temporary relation forks
Date: 2025-06-01 02:22:25
Message-ID: aDu5Ye-Q1mTGQU2Z@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 31, 2025 at 01:26:14PM +0700, Daniil Davydov wrote:
> Not yet. I proceed from the assumption that if the temp_buffers
> parameter is set to a large value (some users set it to more than a
> gigabyte), then the vast majority of time is spent iterating through
> the local buffers.
> Thus, if we reduce the number of iterations from N to (for example)
> N/10, we can get a 10x increase in performance. Of course, this is a
> super rough assumption, but I think you understand my point.
> In the near future I will prepare a patch for the idea above and try
> to do some measurements. If there is a significant difference, I will
> definitely let you know.
>
> Anyway, first I suggest committing the current patch.

I doubt that it would be a good idea to apply a patch "just" because
it looks like a good idea. It is important to prove that something is
a good idea first.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2025-06-01 02:43:30 Re: tighten generic_option_name, or store more carefully in catalog?
Previous Message Tom Lane 2025-06-01 01:12:53 Re: tighten generic_option_name, or store more carefully in catalog?