pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedVulnerability
5+ messages / 4 participants
[nested] [flat]
* Vulnerability
@ 2023-11-24 05:17 SOzcn <selahattinozcnma@gmail.com>
0 siblings, 3 replies; 5+ messages in thread
From: SOzcn @ 2023-11-24 05:17 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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.
Have a great day!
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vulnerability
@ 2023-11-24 07:41 Laurenz Albe <laurenz.albe@cybertec.at>
parent: SOzcn <selahattinozcnma@gmail.com>
2 siblings, 0 replies; 5+ messages in thread
From: Laurenz Albe @ 2023-11-24 07:41 UTC (permalink / raw)
To: SOzcn <selahattinozcnma@gmail.com>; pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vulnerability
@ 2023-11-24 08:19 Thomas Kellerer <shammat@gmx.net>
parent: SOzcn <selahattinozcnma@gmail.com>
2 siblings, 0 replies; 5+ messages in thread
From: Thomas Kellerer @ 2023-11-24 08:19 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vulnerability
@ 2023-11-24 14:15 Ron Johnson <ronljohnsonjr@gmail.com>
parent: SOzcn <selahattinozcnma@gmail.com>
2 siblings, 1 reply; 5+ messages in thread
From: Ron Johnson @ 2023-11-24 14:15 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Fri, Nov 24, 2023 at 12:18 AM SOzcn <selahattinozcnma@gmail.com> wrote:
> 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.
>
Postgresql minor releases are *cumulative*: every new minor release
contains all the fixes from every older release.
That's how all packaged Linux software works.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Vulnerability
@ 2023-11-24 17:22 SOzcn <selahattinozcnma@gmail.com>
parent: Ron Johnson <ronljohnsonjr@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: SOzcn @ 2023-11-24 17:22 UTC (permalink / raw)
To: Ron Johnson <ronljohnsonjr@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
That was what I wanted to hear, thanks.
Have a nice day!
Ron Johnson <ronljohnsonjr@gmail.com>, 24 Kas 2023 Cum, 17:15 tarihinde
şunu yazdı:
> On Fri, Nov 24, 2023 at 12:18 AM SOzcn <selahattinozcnma@gmail.com> wrote:
>
>> 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.
>>
>
> Postgresql minor releases are *cumulative*: every new minor release
> contains all the fixes from every older release.
>
> That's how all packaged Linux software works.
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2023-11-24 17:22 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-11-24 05:17 Vulnerability SOzcn <selahattinozcnma@gmail.com>
2023-11-24 07:41 ` Laurenz Albe <laurenz.albe@cybertec.at>
2023-11-24 08:19 ` Thomas Kellerer <shammat@gmx.net>
2023-11-24 14:15 ` Ron Johnson <ronljohnsonjr@gmail.com>
2023-11-24 17:22 ` SOzcn <selahattinozcnma@gmail.com>
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