pg.ddx.io  pgsql-pkg-yum@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hans Buschmann <buschmann@nidsa.net>
To: devrim@gunduz.org <devrim@gunduz.org>
To: pgsql-pkg-yum@lists.postgresql.org <pgsql-pkg-yum@lists.postgresql.org>
Subject: Re: Fedora 45 release timing
Date: Wed, 4 Nov 2026 11:13:31 +0000
Message-ID: <9998a87378fa43ce9102b3eac3be387c@nidsa.net> (raw)

Hello Devrim,


Given the current delay of Postgres 19 and the ongoing intense bug hunting caused by LLM AI activity I can understand the delay of more than a week.


But the experience of real world users on development and production should be much smoother then that:



I use Fedora Server for production for about 10 years, mostly on virtual machines and some bare metals.


In my experience running postgres on fedora server never causes trouble (like no installation, missing libraries). Even manual compiling with meson is very smooth, some newer compililer warnings of the leading edge GCC compiler where reported and quickly fixed. I always test and self-compile the freshest beta1 of postgres to ensure the compatibility with our application.


This all leads me to the main point: the repositories for a new fedora release should be provided when fedora beta is released !!!


-- this is well planned in advance

-- it has a freeze of new features, so the tooling should be identical/near the same as for general release

-- this gives the opportunity to test postgres on the new release

-- this eliminates the work pressure on fedora GA release date (which may slip)

-- after fedora GA the beta installation is easily converted to the final version by dnf upgrade

-- the availability should be restricted to official releases, no beta/rcs, perhaps by skipping the oldest release soon going EOL


This practice is followed for a long time by remis's RPM repository concerning php:

-- you have early access to beta/rc versions of the new php, also on the upcomming fedora release.


The work to be done should be no different to the after-GA-providing, only 6 to 8 weeks earlier. Tools should work flawlessly.


The problems arise when you upgrade fedora without any PGDG RPMs for postgres available (here 44 to 45):


-- Error messages error 404 of RPMs not found

-- automatic install/update from the PGDG Postgres installation to the fedora internal installation packages, which is easily overseen between about 1000++ update packages

-- perhaps version regression because of fedora not providing the newest minor version.

-- different installation paths, logging, configuration, setup procedure etc.

-- manual removal (of fedora provided packages) triggers often the removing of other required packages (like perl), which must be reinstalled later on

-- users visiting the website don't find a corresponding RPM version, albeit Fedora support is claimed.


On the postgres website it can be marked that the support on a beta version of the operating system like fedora (or RHEL, debian etc) is only preliminary until GA is available.


The early availability ensures every user that his tooling for the new operating system is already available (like the important external tools postgres, php etc) so that the OS upgrade can be planned smoothely!!


The same arguments ar valid for the other operating systems...



One last remark:


In time of a minor release of postgres (normally at the scheduled dates) ALL parts of the new code should be provided, especially the libpq library. In the past libpq arrived more then a wek later, so new uncertainities of administration, supervising, pending security patches etc.



Thank you


Hans Buschmann

view thread (4+ messages)  latest in thread

Message-ID: <9998a87378fa43ce9102b3eac3be387c@nidsa.net>
Permalink:  ../9998a87378fa43ce9102b3eac3be387c@nidsa.net/
Also on:    postgresql.org/message-id/9998a87378fa43ce9102b3eac3be387c@nidsa.net

 · 

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-pkg-yum@postgresql.org
  Cc: buschmann@nidsa.net, devrim@gunduz.org
  Subject: Re: Fedora 45 release timing
  In-Reply-To: <9998a87378fa43ce9102b3eac3be387c@nidsa.net>
  References: <9998a87378fa43ce9102b3eac3be387c@nidsa.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