From: Laurenz Albe <laurenz.albe@cybertec.at>
To: SOzcn <selahattinozcnma@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Vulnerability
Date: Fri, 24 Nov 2023 08:41:25 +0100
Message-ID: <2213e9540a898e8ccba463ff3e1f109f56805bc8.camel@cybertec.at> (raw)
In-Reply-To: <CAJyV5AbM9Sev45nZASMD1rZ=MzRORgUfq_=UvnvGs090zB+BHQ@mail.gmail.com>
References: <CAJyV5AbM9Sev45nZASMD1rZ=MzRORgUfq_=UvnvGs090zB+BHQ@mail.gmail.com>
On Fri, 2023-11-24 at 08:17 +0300, SOzcn wrote:
> 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.
What you wrote is pretty incomprehensible.
Could you describe your actual problem?
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, selahattinozcnma@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Vulnerability
In-Reply-To: <2213e9540a898e8ccba463ff3e1f109f56805bc8.camel@cybertec.at>
* 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