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 1su8Lb-004S0e-Jf for pgsql-hackers@arkaria.postgresql.org; Fri, 27 Sep 2024 10:37:16 +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 1su8La-0073h5-Re for pgsql-hackers@arkaria.postgresql.org; Fri, 27 Sep 2024 10:37:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1su8La-0073gx-Bt for pgsql-hackers@lists.postgresql.org; Fri, 27 Sep 2024 10:37:14 +0000 Received: from forwardcorp1a.mail.yandex.net ([178.154.239.72]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1su8LV-001LJy-W6 for pgsql-hackers@lists.postgresql.org; Fri, 27 Sep 2024 10:37:13 +0000 Received: from mail-nwsmtp-smtp-corp-main-80.iva.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-80.iva.yp-c.yandex.net [IPv6:2a02:6b8:c0c:1a13:0:640:f32:0]) by forwardcorp1a.mail.yandex.net (Yandex) with ESMTPS id C972460DEB; Fri, 27 Sep 2024 13:37:09 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6b8:b081:8810::1:b]) by mail-nwsmtp-smtp-corp-main-80.iva.yp-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id 8bTB5V0IXuQ0-I7nvoh16; Fri, 27 Sep 2024 13:37:09 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1727433429; bh=JFCBtw14ivBiqj1RSRhd5KR/UKQ3xlDb56k2+UkHuR0=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=wmLAeZishBw6/cu+OVjuNMAiEZlfgeuqGwV4SJO3HEbftjfT+PbMUJDZThARx1/N9 8FXeeBBGQRjm4e7Aco4btj9WHqV/4pMkP9cOWPmTQwocBhqRir6NL3j2hR/iZKyy16 m3D/3ObamhDto9kgIAXPOOiP+sPOq8/vq7OpVDS0= Authentication-Results: mail-nwsmtp-smtp-corp-main-80.iva.yp-c.yandex.net; dkim=pass header.i=@yandex-team.ru Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: Truncate logs by max_log_size From: "Andrey M. Borodin" In-Reply-To: <94d53a41-d1f5-4fd1-8d1e-ff36ac569848@app.fastmail.com> Date: Fri, 27 Sep 2024 13:36:58 +0300 Cc: diPhantxm , pgsql-hackers@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <4DA5A159-39FD-47DB-95E5-A4F65BC5782A@yandex-team.ru> References: <94d53a41-d1f5-4fd1-8d1e-ff36ac569848@app.fastmail.com> To: Euler Taveira X-Mailer: Apple Mail (2.3776.700.51) X-Yandex-Filter: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 27 Sep 2024, at 03:30, Euler Taveira wrote: >=20 > Let's say you arbitrarily provide max_log_size =3D 100 Consider max_log_size =3D 10Mb. The perspective might look very = different. It=E2=80=99s not about WHERE anymore. It's a guard against = heavy abuse. The feature looks very important for me. Best regards, Andrey Borodin.=