On 10/24/25 18:53, Tom Lane wrote:
> David Rowley <dgrowleyml@gmail.com> writes:
>> On Sat, 25 Oct 2025 at 13:40, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>>> 1) From previous posts to this list folks have mentioned their
>>> organizations prohibit touching anything less then a GA or maybe a late
>>> RC. That comes from on high and I doubt the folks issuing the orders are
>>> on this list.
>
>> That seems bizarre to me. If they want new releases of PostgreSQL to
>> be as stable as possible as early as possible, then beta and RC are
>> much better times to test than .0 is.
>
> I think the folks issuing that sort of order believe that testing is
> Somebody Else's Problem. The folly of that approach is pretty evident
> to those of us toiling in the software trenches, but maybe not so much
> from the C-suite.
Yes and no. Yes someone needs to test new software, no that is not for
everyone. The presence and uptake of LTS software indicates that being
on the edge of development is something folks would like to avoid. I
know as I use LTS versions of Ubuntu and Django for that very reason, I
want to get work done without worry about having to pick up 'shiny bits
and pieces'. That being said, it allows me the time to kick the tires on
new software, of current interest Polars and Duckdb. It comes down to
time available and what you want to spend that time on. That could very
well mean making testing 'Somebody Else's Problem', in the way that
Postgresql Core has made packaging some else's problem:
https://www.postgresql.org/message-id/427155.1755538776@sss.pgh.pa.us
"
The core project wouldn't document that, because we just ship source
code not RPMs. There might be a README in the core postgresql RPM
package telling you what's what.
"
>
> regards, tom lane
--
Adrian Klaver
adrian.klaver@aklaver.com
