> Part of why delaying is helpful is that more people will actually install the release than they do during the beta/RC cycle
Unless everybody starts waiting for .1 :)
> was not necessarily because of significant bugfixing in 19
They discovered some serious bugs in new features which weren't really solvable in a way the devs were comfortable with (with regards to long-term maintainability and stability). So some of the new features were rolled back and that process also took some time.
Yep, agreed its bad if everyone does it - but e.g. you could upgrade pre-prod / staging and only do prod once the 19.1 release is out.
To clarify what I meant with the second part: If you look at e.g. SQL/PGQ it was reverted pretty late (beta4), but that revert doesn't mean that other features don't have bugs that are yet to be ironed out. e.g. just this morning a bugfix went in that can crash EXPLAIN (BUFFERS) (without ANALYZE) when you have auto_explain turned on [0]. Edge case, but could happen, and the fix will only be in 19.1 in February 2027.
[0]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...