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 1v1PHM-008JcM-1j for pgsql-general@arkaria.postgresql.org; Wed, 24 Sep 2025 13:11:28 +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 1v1PHK-00DCLz-IC for pgsql-general@arkaria.postgresql.org; Wed, 24 Sep 2025 13:11:26 +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 1v1PHK-00DCLm-60 for pgsql-general@lists.postgresql.org; Wed, 24 Sep 2025 13:11:26 +0000 Received: from mail-oo1-xc29.google.com ([2607:f8b0:4864:20::c29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v1PHI-002BXF-0N for pgsql-general@lists.postgresql.org; Wed, 24 Sep 2025 13:11:25 +0000 Received: by mail-oo1-xc29.google.com with SMTP id 006d021491bc7-6339c780fdaso781973eaf.2 for ; Wed, 24 Sep 2025 06:11:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758719484; x=1759324284; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=UTKG/4RtU/7fBwCSRajKQdpd7SMVT46qUevu0UaTAEM=; b=DIiigvgoB/iLYuKvwRsTjBAkyAicGOpEcNenWFAWrvtZZrM0LBY9j6Yr8GMu1rkZDX wEXCRtpMpjFhDwAkKKHPwp+hCqcQBzvFfGr7gbcACcwIu1xUFKt7VZfF6NV128gt7B1P GDky9uE/7o9HeDdn1tJUyr8TlZXA/wZ2CroQIMd7j/iSo+BeU26fRYuZ0zn+6wxEM8U8 SUncMHMgCIE5J6XvnKTUhtTYVi6jXndPDPKqNwoU3/1PBypGgjXfKybjbaY4a2r/XKGi mDD2saOV9zepTwdmqBoPPH8+77v9dky1qL8emCXa1/SgJUPEOqEBw0Pqjt+G5PCsKOZ+ 8EJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758719484; x=1759324284; h=cc: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=UTKG/4RtU/7fBwCSRajKQdpd7SMVT46qUevu0UaTAEM=; b=R15iNDxWNeR6c5Z4Y3mf+hoCMZOeYU30CIF8OGpG48AUGu/NKMcfs45vkELEiUekDU p+lvu/ooPVTcd9a/gL8w2qjBVzZbFk04k0IQFmc/7IEL1EMI/lw6+I/OCgyIswljtm7y qrnHS/apnm3RD6MjZYsP5NayrvNTkGg81ypm415F3CKpjo+BtGTwJ+uhjHqXgDVN4A0G VELu5OCr3XXUhAWhhmbDHMroDZVhluDBxgxk5+8+gq1lomZFpOEQ6W+RyZR2dzf/3lvE A7NK6Yp92wmubWhMZVSOwcEfL8J5uNPWCP0pV42Tv2hyjA/Wn2z7hwncxIykt/sIJLWE MeLA== X-Forwarded-Encrypted: i=1; AJvYcCUyJD6pc5yqbh76zCJZ5lyFhzdfp3Qz7oqeSR8UoKfOYxj0v7BL8Te8TpTkWXNakBkT7dQDKbm0xK6O72TS@lists.postgresql.org X-Gm-Message-State: AOJu0YxQFr80QYP1YdzxqNXpOQTu8040b03Woz9haYMsnQRGYNaepCs4 T6qFqhMcla3YVDMAa0eGyhOvUHNmtWOl1bkb9vAwLM6TpZIVkixrEn/+gHX4hHDlj0fMBXFFJON kcA3ItssE8o6pVqXCiL22W4SKQkF3iB0= X-Gm-Gg: ASbGncs9OJaFIrr0irtAAgqSpCxsbTO5cdr9zlPBKonwSsyIjZF2NUzSqm3+4ujXJxG A70FMmcUvbZTQK7WylwkZJ9YjjZPdMStKh3wsDjkUg2F/qTOuGO7pHMHAUfarLkYO21Wd745PSO oKEC+DQK5oKvPhopJ4a+Fjp90wnatszmUcrHn1k9PhprfZi8to799OuRyadLBEz2yqUGVMZDdG8 XUxFoSj X-Google-Smtp-Source: AGHT+IEdEJKdqDNrv/tBfDQNMP2MxAuMmRVjX+iF1r8/uy0jul/PdOvdMLAs4OicINEX1dVKYQ/v5LKIKykTn2UqqpE= X-Received: by 2002:a05:6808:2203:b0:43b:294a:9145 with SMTP id 5614622812f47-43f2d3c915dmr3608411b6e.23.1758719483636; Wed, 24 Sep 2025 06:11:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 24 Sep 2025 09:11:11 -0400 X-Gm-Features: AS18NWADzNjH-hk6F-ermzNbr1LDZ3VPpPDZTKxBZEWK_iH74SbVJKyWd35Az90 Message-ID: Subject: Re: Query on Patch and Upgrade History in PostgreSQL To: Laurenz Albe Cc: loganathan P , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000014f56b063f8bca0e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000014f56b063f8bca0e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Sep 24, 2025 at 6:37=E2=80=AFAM Laurenz Albe wrote: > On Wed, 2025-09-24 at 13:47 +0530, loganathan P wrote: > > How do I find the date and time of applied minor patches and upgrades i= n > a PostgreSQL database level? > > This information is not stored inside the database. > A minor upgrade just means replacing the files and restarting the server. > > If you are using a package manager, perhaps you can find the information > there. > On PM-based systems, you can. $ rpm -q --last postgresql17 postgresql17-17.6-1PGDG.rhel8.x86_64 Sun 24 Aug 2025 08:57:02 AM EDT --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000014f56b063f8bca0e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Sep 24, 2025 at 6:37=E2=80=AFAM L= aurenz Albe <laurenz.albe@cy= bertec.at> wrote:
On Wed, 2025-09-24 at= 13:47 +0530, loganathan P wrote:
> How do I find the date and time of applied minor patches and upgrades = in a PostgreSQL database level?

This information is not stored inside the database.
A minor upgrade just means replacing the files and restarting the server.
If you are using a package manager, perhaps you can find the information th= ere.

On PM-based systems, you can.

$ rpm -q --last postgresql17<= br>postgresql17-17.6-1PGDG.rhel8.x86_64 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0S= un 24 Aug 2025 08:57:02 AM EDT

--
Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.
<Redacted> lobs= ter!
--00000000000014f56b063f8bca0e--