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: 
 <CAHJZqBAQaRTyAqNY+H7dP4uZQeOOVePkvB7+z39SU7yHdn8OLg@mail.gmail.com>
References: 
 <CAHJZqBALD244nL_iSBvfr7rKCid-zhe61JYtgZEPSujrixHRzg@mail.gmail.com>
 <22950.1510932311@sss.pgh.pa.us>
 <CAHJZqBAQaRTyAqNY+H7dP4uZQeOOVePkvB7+z39SU7yHdn8OLg@mail.gmail.com>
Comments: In-reply-to Don Seiler <don@seiler.us>
	message dated "Fri, 17 Nov 2017 09:29:31 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23392.1510932969.1@sss.pgh.pa.us>
Date: Fri, 17 Nov 2017 10:36:09 -0500
Message-ID: <23393.1510932969@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Don Seiler <don@seiler.us> writes:
> The difference though is when the client sets that timezone when
> connecting, that's when the error is listed as FATAL and the connections
> fail in 9.6 (and also 9.3 according to the previous thread), where as the
> connections didn't fail in 9.2 and earlier. That's the behavior change I'm
> looking to account for.

Ah, gotcha.  I believe that the FATAL case occurs if the client tries
to set an invalid parameter value within the connection startup packet,
rather than after connecting.  But that behavior hasn't changed in
a long time either.  I think what you need to be looking for is a
client-side change in how/when it sends a desired timezone setting to
the server.

			regards, tom lane


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