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 1sd1oU-00CWv6-Ck for pgsql-in-general@arkaria.postgresql.org; Sun, 11 Aug 2024 06:12:22 +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 1sd1oS-00BEuy-Cp for pgsql-in-general@arkaria.postgresql.org; Sun, 11 Aug 2024 06:12:20 +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 1sd1oS-00BEup-5i for pgsql-in-general@lists.postgresql.org; Sun, 11 Aug 2024 06:12:20 +0000 Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sd1oP-004F0Q-MK for pgsql-in-general@postgresql.org; Sun, 11 Aug 2024 06:12:19 +0000 Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-5ba482282d3so4148250a12.2 for ; Sat, 10 Aug 2024 23:12:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723356736; x=1723961536; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=7U6BysTUnX9HJt3VNki6hjPaxvk0PryxF4T7jatr+pw=; b=guiSOKF/Pgm7rzeDoyNnn54UMKsADHup9sPIH0+otpOwd7eZFS5/Pzewdasc4ntVHs +sMYTcEodkhBXIbBdW2ArjLs/xBehx+0XmFwTSpb20kMohoTqy9QnU8hl21Q7LW7XyZ7 bsXPbzEB847yruVkct9zvLU6Cqj01rviIioUtAxESUxharjZGp/5nThYB17+FM5EqqI3 /zlgK7lakhRwscspHIb8jZjFZxVba1E27dU8P2sodr8ur1EhRva+H1k54GLCB6gtHZik J0EX8Mfrq+IkQ3KCxLUUJGcJF1DLwjY2kXWpIioNkSmAZfcloxIKECgYJWY/UT0J5V4P JjGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723356736; x=1723961536; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=7U6BysTUnX9HJt3VNki6hjPaxvk0PryxF4T7jatr+pw=; b=mjjhjzRpJ6Tb6SVFFvJcaHpPNQsbqQVHKz1BLpF7HJnvWhMjTsCg5ZsOzhW2cnT40D xET0NXec9SM4zUOrHwKT2HRWy0PiheeJr6opOBfIAwjWmW31MRjngRlPt+AZhPAbR3cf dQ+RZb8ZwpUIuMalNVOc5QSRFSJdG2ZhyTxBm3T4BYv1r7HFIPlH/lUAVCPg0KkrtJM6 yEr0XMhxdRbSfHgnxkclotgSVtLJ2hVcNhxwmCnDGwE6E/nEPErR6IIt6lFJ+v289bx2 lQasAiaam4Yzt8JMz2j0QMZUW1QqCl3GusJZ+hirT7Yvqei85FRgucCzr1WNEVF9+xhL PVfQ== X-Forwarded-Encrypted: i=1; AJvYcCW2UTI7UEdu766UHcRKmJiejs6IU/5gUvakORrvE//K16PpJoPR/GRkIo9xKTGTm655ZkpytXTKPx/5Olno8D88wd7ZAh0V6DlRnL4HbYiF X-Gm-Message-State: AOJu0YwR9x1sz029yHyDpBj+7IiK7FL9q8sYi34EESUH138patFMvVkl ElUFmQ6npz/z0IGQrn/MtfG7SnzNu+LxthtU+y9/8+JsjepJ1Vs6hdP8uJPEqcbQV+QX0kIIkuN ecLjso8Sxy9vV/dy4sK/7Sg8NV5U= X-Google-Smtp-Source: AGHT+IHrp5rTzASXRtyzfhVhsTHwiS0BdJzHkSVqLaVdpoQYkeUmLWs30j6OLDBZ5ZuSrJXy6XFy5PYknmniHsws+Io= X-Received: by 2002:a17:906:cae5:b0:a77:dd1c:6273 with SMTP id a640c23a62f3a-a80aa55a47dmr421667266b.12.1723356735878; Sat, 10 Aug 2024 23:12:15 -0700 (PDT) MIME-Version: 1.0 From: Durgamahesh Manne Date: Sun, 11 Aug 2024 11:43:58 +0530 Message-ID: Subject: autovacuum freeze recommendations at table level To: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org, Christoph Berg Content-Type: multipart/alternative; boundary="000000000000103dcd061f624231" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000103dcd061f624231 Content-Type: text/plain; charset="UTF-8" Hi Respected Team, Could you please let me know that how this freeze parameters work Update query runs on table through which data being modified daily in this case Total records in table is about 20lakhs current setting for this table is Access method: heap if it reaches > 0.1*2000000+1000 = 2,10,000 as per the formula autovacuum triggers Options: fillfactor=85, autovacuum_vacuum_cost_delay=0, autovacuum_vacuum_cost_limit=3000, parallel_workers=6, autovacuum_vacuum_scale_factor=0.1, autovacuum_vacuum_threshold=1000, autovacuum_freeze_max_age=20000000, autovacuum_multixact_freeze_max_age=20000000, autovacuum_freeze_min_age=0 How autovacuum freeze parameters work.Give me some recommendations to improve the performance better than now Ex :ALTER TABLE table SET ( autovacuum_freeze_max_age = 20000000,(2 crores) autovacuum_multixact_freeze_max_age = 20000000,(2 crores) autovacuum_freeze_min_age = 0 ); Regards, Durga Mahesh --000000000000103dcd061f624231 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0 Respected Team,

Could you plea= se=C2=A0let me know that how this freeze parameters work
Update q= uery runs on table=C2=A0 through which data being modified daily in this ca= se
Total records in table is about 20lakhs
current sett= ing for this=C2=A0table is=C2=A0
Access method: heap
if= it reaches > 0.1*2000000+1000 =3D 2,10,000 as per the formula autovacuu= m triggers
Options: fillfactor=3D85, autovacuum_vacuum_cost_delay=3D0, a= utovacuum_vacuum_cost_limit=3D3000, parallel_workers=3D6, autovacuum_vacuum= _scale_factor=3D0.1, autovacuum_vacuum_threshold=3D1000, autovacuum_freeze_= max_age=3D20000000, autovacuum_multixact_freeze_max_age=3D20000000, autovac= uum_freeze_min_age=3D0

How autovacuum freeze p= arameters work.Give me some recommendations to improve the performance bett= er than now=C2=A0
Ex :ALTER TABLE table SET (
=C2=A0 =C2=A0aut= ovacuum_freeze_max_age =3D 20000000,(2 crores)
=C2=A0 =C2=A0autovacuum_m= ultixact_freeze_max_age =3D 20000000,(2 crores)
=C2=A0 =C2=A0autovacuum_= freeze_min_age =3D 0
);
Regards,
Durga Mahesh=C2=A0
--000000000000103dcd061f624231--