From: Thomas Kellerer <shammat@gmx.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Vulnerability
Date: Fri, 24 Nov 2023 09:19:56 +0100
Message-ID: <85a164d9-d821-42cf-82ad-5719f633ecf8@gmx.net> (raw)
In-Reply-To: <CAJyV5AbM9Sev45nZASMD1rZ=MzRORgUfq_=UvnvGs090zB+BHQ@mail.gmail.com>
References: <CAJyV5AbM9Sev45nZASMD1rZ=MzRORgUfq_=UvnvGs090zB+BHQ@mail.gmail.com>
SOzcn schrieb am 24.11.2023 um 06:17:
> Hello Team, first of all I hope everything going well for you guys.
>
> As errors are corrected in a major version of PostgreSQL, new
> adjustments are made and that bug disappears. For example, there was
> an X bug on v14, this problem was fixed in 14.2, etc. Do I only need
> to upgrade when applying an additional patch for this? Or should we
> pull my files from the repo? I would appreciate it if you could
> explain exactly what should be done in such matters.
In general you should upgrade to the latests minor version as soon as possible.
https://www.postgresql.org/support/versioning/
For Postgres 14 this would be 14.10 - and that will include the fixes introduced in 14.2
There is no need install the intermediate version if you still use something older than 14.9 - just install 14.10
Regards
Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Vulnerability
In-Reply-To: <85a164d9-d821-42cf-82ad-5719f633ecf8@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox