Cost-based delay for (other) maintenance operations

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Cost-based delay for (other) maintenance operations
Date: 2025-02-12 20:11:21
Message-ID: C3452AD2-8B57-472B-AE0D-C1AC40CF39EE@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

We've run into multiple situations recently where clients were effectively unable to run CREATE INDEX or REINDEX (CONCURRENTLY or otherwise) due to the load that they imposed on the system, mostly in I/O. I'd like to propose a cost-based delay system for maintenance operations such as these, paralleling the system for (auto)VACUUM. Before I pull together a code proposal, I wanted to preflight the idea to make sure it has not been considered and rejected already, or find out if anyone is working on it already.

Browse pgsql-hackers by date

  From Date Subject
Next Message James Hunter 2025-02-12 20:26:45 Re: AIO v2.3
Previous Message Tomas Vondra 2025-02-12 20:07:51 Re: BitmapHeapScan streaming read user and prelim refactoring