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
Date: Fri, 17 Nov 2017 10:36:09 -0500
Message-ID: <23393.1510932969@sss.pgh.pa.us> (raw)
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, don@seiler.us
Subject: Re: FATAL: invalid value for parameter "TimeZone" after upgrade from 9.2 to 9.6
In-Reply-To: <23393.1510932969@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox