pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: gayathri ramesh <17gayathriramesh@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Request for information about postgres version 15.2 stability
Date: Tue, 18 Apr 2023 18:04:35 +0200
Message-ID: <5100adfe28807f9278ee796c52181f2a4cc71b3d.camel@cybertec.at> (raw)
In-Reply-To: <CAJssgL==3TvFmcJDEvX7xbts_6AndYNKxyqy+mVkoJ9b7bMNHg@mail.gmail.com>
References: <CAJssgL==3TvFmcJDEvX7xbts_6AndYNKxyqy+mVkoJ9b7bMNHg@mail.gmail.com>

On Tue, 2023-04-18 at 12:26 +0530, gayathri ramesh wrote:
> Our company is currently supporting around 100+ postgres databases and we are planning
> to upgrade to version 15.2. We want to ensure that there are no major critical bugs
> that could impact our production systems.
> 
> I would appreciate if you could provide us with information about the stability of
> postgres version 15.2. We are particularly interested in knowing if there are any
> known critical bugs or issues that could potentially impact the system.

To see a list of bugs fixed since 15.2 came out, look at the commit log:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=shortlog;h=refs/heads/REL_15_STABLE

Release 15.2 came out on 2023-02-09.

We don't have any information about yet undiscovered PostgreSQL bugs.

We believe that PostgreSQL 15.2 is a great and stable database, but we are biased.

Yours,
Laurenz Albe





view thread (6+ messages)  latest in thread

Message-ID: <5100adfe28807f9278ee796c52181f2a4cc71b3d.camel@cybertec.at>
Permalink:  ../5100adfe28807f9278ee796c52181f2a4cc71b3d.camel@cybertec.at/
Also on:    postgresql.org/message-id/5100adfe28807f9278ee796c52181f2a4cc71b3d.camel@cybertec.at

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: laurenz.albe@cybertec.at, 17gayathriramesh@gmail.com
  Subject: Re: Request for information about postgres version 15.2 stability
  In-Reply-To: <5100adfe28807f9278ee796c52181f2a4cc71b3d.camel@cybertec.at>
  References: <CAJssgL==3TvFmcJDEvX7xbts_6AndYNKxyqy+mVkoJ9b7bMNHg@mail.gmail.com> <5100adfe28807f9278ee796c52181f2a4cc71b3d.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