Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tQs7r-005iTl-8g for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Dec 2024 17:58:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tQs7q-003kQ6-9o for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Dec 2024 17:58:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tQs7q-003kPv-04 for pgsql-hackers@lists.postgresql.org; Thu, 26 Dec 2024 17:58:21 +0000 Received: from relay5-d.mail.gandi.net ([2001:4b98:dc4:8::225]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tQs7n-000gJy-1r for pgsql-hackers@postgresql.org; Thu, 26 Dec 2024 17:58:20 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 80C821C0002; Thu, 26 Dec 2024 17:58:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1735235893; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bYk62rQdDaTYYZc4um1oIu8jNd6ZP5Eu/DL+YsjIMPc=; b=blJ7eO+2zWdT1bxd4t3eq5XhqzRtUOlyAp2iMvfvBnkaQ7nNTMr/zyPsUf8vmVEPvU6MhV +jpX38eANxI5s1m/LzYmnOG5OGtR1iYCBv3AIYBZ3UJC9X7Hn9Bp2wLf6yfkstwp/mnF+/ 8Hxi1rNGu8stiqawRxCUyESD4BTTZrNyqi5LQcYp3FM5eG0OyetXAPjYc8sVPbWq0b0VDW MmaqycWA4D+aXpbYX44stiKuO/009UHZkF5/oqQCzG2izJWTyC3wOBW15DCM1zb5D6VDxr 5gWq2mhr0xdL86Zmc5X+pD6xStRtSEGQ1N6NbMG8o31m6JTde7TD/CMIboi8QQ== Message-ID: Date: Thu, 26 Dec 2024 18:58:11 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: PoC: history of recent vacuum/checkpoint runs (using new hooks) To: wenhui qiu , Robert Treat Cc: PostgreSQL Hackers References: <8df7cee1-31aa-4db3-bbb7-83157ca139da@vondra.me> Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/26/24 17:00, wenhui qiu wrote: > Hi  >     > As far as I know, more than 10,000 tables  of instances  are often > encountered, > So I insist that the maximum can be appropriately increased to 256MB, > Can be more adaptable to many table situations > If 128MB is insufficient, why would 256MB be OK? A factor of 2x does not make a fundamental difference ... Anyway, the 128MB value is rather arbitrary. I don't mind increasing the limit, or possibly removing it entirely (and accepting anything the system can handle). regards -- Tomas Vondra