| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Reports on obsolete Postgres versions |
| Date: | 2024-03-11 20:37:49 |
| Message-ID: | Ze9rnSQ4jAOpvF7k@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I am seeing an increasing number of bug/problem reports on obsolete
Postgres versions, either not running a superseded minor version, or
running an unsupported major version.
What can we do to reduce such reports, or at least give a consistent
response? It is very helpful that we have this web page, and I have
made a habit of pointing reporters to that page since it has all the
information they need:
https://www.postgresql.org/support/versioning/
This web page should correct the idea that "upgrades are more risky than
staying with existing versions". Is there more we can do? Should we
have a more consistent response for such reporters?
It would be a crazy idea to report something in the logs if a major
version is run after a certain date, since we know the date when major
versions will become unsupported.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2024-03-11 20:41:29 | Re: Confine vacuum skip logic to lazy_scan_skip |
| Previous Message | Corey Huinker | 2024-03-11 20:08:05 | Re: Statistics Import and Export |