Re: Known issues on PostgreSQL server 8.1.19

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Known issues on PostgreSQL server 8.1.19
Date: 2015-12-18 16:22:12
Message-ID: 20151218162212.GR2618@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thomas Munro wrote:

> How crazy would it be to emit a log message when Postgres comes up and
> discovers that time has moved past the advertised
> known-five-years-in-advance EOL date for the executable's major
> release? (And perhaps another kind of message when the executable's
> minor release is certainly too old, though I have no idea when that
> would be...)

I don't think it's likely that sysadmins that leave their systems
without updates for so long would even consider the idea of looking at
the log files -- much less look for warnings emitted at server start.

People familiar with Postgres would probably notice such a warning, of
course, but we would immediately notice that the minor/major version is
out support just as well.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2015-12-18 17:24:13 Re: BUG #13681: Serialization failures caused by new multixact code of 9.3 (back-patch request)
Previous Message Tom Lane 2015-12-18 15:43:42 Re: to_date() not works as described for pattern DD & HH