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 1uio8X-00G4da-HV for pgsql-admin@arkaria.postgresql.org; Mon, 04 Aug 2025 05:53:29 +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 1uio8W-00GHuL-6V for pgsql-admin@arkaria.postgresql.org; Mon, 04 Aug 2025 05:53:28 +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 1uio8V-00GHuD-MP for pgsql-admin@lists.postgresql.org; Mon, 04 Aug 2025 05:53:27 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uio8T-000dxw-0o for pgsql-admin@lists.postgresql.org; Mon, 04 Aug 2025 05:53:27 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-433f3bc84e0so1174016b6e.3 for ; Sun, 03 Aug 2025 22:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754286803; x=1754891603; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Fxec1g2e0ATyO1WIJSPY+SjC/YYSalTNUXlpP7C192g=; b=Wj3VVzvVd5W4x4j9GHt4IWCgmt3cZ/DH9wZLKflTUy1azhgq9sk6qmpZO5aAzHcXKn gkChQQjiMrQ8GEkz2/JESvkcY73Q8IBKDyq1ijmDUAppBAYtamyYZBPt+CDJ70A6lbuO /PDD4b1IeeJgkiN0eFOkvUhE2YoBTIH9zocBiO3y2AVLTB+qkMFJt8mJAHsH6vJKQ1mI Xnu1zWLnXeRqF7D+eTt/sxQMr2cdEAkyZ7CPyW6ERcj5ilrPnGwZYpWoEU8uzyvhMKmv wYfLjpwboThT8dDSrF4EM8vp92XvYyO7UeOCIDiN8+6uAPGQ4Bg2N9B3J4kAHmZZqR0y 6rYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754286803; x=1754891603; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Fxec1g2e0ATyO1WIJSPY+SjC/YYSalTNUXlpP7C192g=; b=gcEcI81ntS0bsR6qM9Jy1COmH7JPp10XIUYV2y0yly4KW0Wvs7eZyd8j11/Lu4n3Vf XZgDtjVzxLs1Dw0O4eXTzYmYiDW+2JzarpXcDqXEbPIHN9Mr6H5M+1/Xj1o9zlJN+P5g qMkE46v1Dj8g+SpkZL9aSg5zfjsJUvNbqCxcVjELdVkxfHRFVuwRD59wAviVX2YgKrVP 85dIdq3kB90TKCvyzDsizc1P1j5r4je9Gjh8tNchsHKYpR1b+gFnt88MvllXx0FjcC2+ X0Hij6yG8zkgLy9ym5mEJmAGbPUCE8t5N7HDVZeIOa0BW4YWF7ObKB+6llVHqSwa+gns nsWA== X-Gm-Message-State: AOJu0YxFs368zLvwDOK31EtLDEvulg26TAOxhrGj1CvCuWewk3mgH/2I mfF1NCMY2VoaQXnALHYL/gULf5oIslYKT8SgCEwfZa/WgI4INsgiquVlLub0TABwoWgi/G861w3 jWVGDfd8y7K1yKguH/CmvACvVQVEZYVbxRw== X-Gm-Gg: ASbGncvHx8x92++7Kw3Cay0GJSP7Ui9DnPixpjGzWF5+XzRXydFREKFdymPypvQQU2v 0geCHCYEhIFJ+kE5qxXKdwiZjWDdrT9xTa5U99/PeFAw+zpJZqG528EKDeLJLuorZif0LHDmr2t ByV/30IZuFDKmauRc2jGie3lzWg2hgWAa9+5zXS+IT1SzxqZl492FQoWiX5IT3kj8kAluMNlSFI 4364gyUPn524sqoCrQ= X-Google-Smtp-Source: AGHT+IFA8/1yhkBxVZJ/gPptair7oMkfpQm5G7IY4M5/aP2fiz6UoHNj7JZ9w5eHkUb/dOo1sGYJjVIFri0SkPml5CQ= X-Received: by 2002:a05:6808:181f:b0:408:e5f8:9e2b with SMTP id 5614622812f47-433f023b7bbmr4789494b6e.10.1754286803406; Sun, 03 Aug 2025 22:53:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Mon, 4 Aug 2025 01:53:12 -0400 X-Gm-Features: Ac12FXxmAGaGo3GYpWWdnerV1Qea7kZ5m10OZCtDH7_VbYUXvaRBk5IZvAVOLts Message-ID: Subject: Re: Vacuuming System DBs like postgres, template1 To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000c0552b063b83b9cd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c0552b063b83b9cd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Aug 4, 2025 at 12:48=E2=80=AFAM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Sun, Aug 3, 2025 at 8:45=E2=80=AFPM OMPRAKASH SAHU > wrote: > >> On few large DBs we run vacuum analyze manually as well, and I do see fe= w >> people vacuuming the template1 db or postgres db also >> >> So just wanted to know vacuum system dbs is required or not? >> >> Pretty sure the answer is yes - though letting auto-vacuum do it is > sufficient - since something has to update the catalog column that > indicates the oldest transaction the database is aware of. There isn't a > value for that which means "everything has been frozen" since it doesn't > get updated in the normal course of activity. > template1 needs to be regularly vacuumed? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000c0552b063b83b9cd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Aug 4, 2025 at 12:48=E2=80=AFAM D= avid G. Johnston <david.g.= johnston@gmail.com> wrote:
On Sun, Aug 3, 2025= at 8:45=E2=80=AFPM OMPRAKASH SAHU <sahuop2121@gmail.com> wrote:
On few large DBs we run vacuum analy= ze manually as well, and I do see few people vacuuming the template1 db or = postgres db also=C2=A0

S= o just wanted to know vacuum system dbs is required or not?

Pretty sure the answer is yes - though letting auto-vacuum do it is= sufficient - since something has to update the catalog column that indicat= es the oldest transaction the database is aware of.=C2=A0 There isn't a= value for that which means "everything has been frozen" since it= doesn't get updated in the normal course of activity.

template1 needs to= be regularly vacuumed?

--
Death to <Redacted>, and butter sauce.
Don't boil me= , I'm still alive.
<Redacted> lobster!
--000000000000c0552b063b83b9cd--