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

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> We don't have any information about yet undiscovered PostgreSQL bugs.

Indeed.

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

One moderately objective way to see how stable a release branch is
is to count how many commits fix bugs in that branch but not any
older branch.  If a bug would be problematic for you but it also
appears in (say) v14 and v13, then choosing to use one of those
branches instead of v15 wouldn't have saved you.  Also, if a commit
goes back that far, it means that the bug escaped detection for
multiple years in production, which suggests that it is minor and/or
doesn't affect many people.  (I hasten to add that we do find some
bugs that are both old and serious.)

A quick review of commits since 15.2 says that practically all of the
ones that don't also affect v14 or before have to do with glitches in
new-in-15 features, such as the MERGE command.  Which is code you
wouldn't be using anyway if your application would be satisfied with
an older branch.  So I'd judge that 15 is pretty stable at this point,
and there is very little reason to prefer any older branch.

If you want to do your own analysis along these lines, the gitweb
interface isn't especially friendly for comparing commit logs of
different branches.  I'd suggest using our git_changelog script:

git clone https://git.postgresql.org/git/postgresql.git
cd postgresql
src/tools/git_changelog >../pg-revision-history

This produces output that collates matching commits in different
branches.

			regards, tom lane





view thread (6+ messages)  latest in thread

Message-ID: <2664328.1681835752@sss.pgh.pa.us>
Permalink:  ../2664328.1681835752@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2664328.1681835752@sss.pgh.pa.us

 · 

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

* 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