From: Tom Lane <tgl@sss.pgh.pa.us>
To: Don Seiler <don@seiler.us>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: FATAL: invalid value for parameter "TimeZone" after upgrade from
 9.2 to 9.6
In-reply-to: 
 <CAHJZqBALD244nL_iSBvfr7rKCid-zhe61JYtgZEPSujrixHRzg@mail.gmail.com>
References: 
 <CAHJZqBALD244nL_iSBvfr7rKCid-zhe61JYtgZEPSujrixHRzg@mail.gmail.com>
Comments: In-reply-to Don Seiler <don@seiler.us>
	message dated "Fri, 17 Nov 2017 09:07:55 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <22949.1510932311.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Nov 2017 10:25:11 -0500
Message-ID: <22950.1510932311@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Don Seiler <don@seiler.us> writes:
> My issue is more or less similar to
> http://www.postgresql-archive.org/Upgrading-from-PG-8-3-3-to-9-3-4-FATAL-=
invalid-value-for-parameter-quot-TimeZone-quot-quot-PST-quot-td5805665.html

> However what I'm looking to answer is why this wasn't fatal in 9.2?

It was.  I don't think PG has ever accepted just "PST" (or "CDT") as a
timezone name.  There's no such entry in the IANA tz database, and it's
not a legal POSIX zone specification --- you'd need at least "PST8" for
it to go through that code path.  I tried it just now on 7.4.30, which is
the oldest version I have on this machine (about 2 years older than 9.2.0)
and it failed as expected:

regression=3D# set timezone =3D 'PST';
ERROR:  unrecognized time zone name: "PST"

Now, it's barely conceivable that you strong-armed 9.2 into accepting
it by making a file or symlink named "PST" in the timezone database
directory of the old installation ... but otherwise, I'm quite certain
it would not have taken it.

			regards, tom lane


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin