Re: drop support for Python 2.3
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Devrim Gündüz <devrim@gunduz.org>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-02-19T18:48:11Z
Lists: pgsql-hackers
Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim@gunduz.org> writes: > On Sun, 2017-02-19 at 10:42 -0500, Tom Lane wrote: >> Relevant question: what version of tcl is installed on those? > 8.4.13 is installed. Hmph. I can't see any relevant-looking source changes between 8.4.13 and 8.4.15, which I have laying about here and which works fine. I wonder if Red Hat is carrying some distro-specific patch that breaks this case? Or conceivably it's timezone dependent? Anyway, my inclination is just to tweak that test a bit so it doesn't trip over the problem. The point of the test is mainly to see if the [clock] command works at all, not to exercise any specific parameter choices. Would you check whether this: $ tclsh % clock format [clock scan "1/26/2010"] -format "%U" gives the expected result "04" on that machine? regards, tom lane
Commits
-
Adjust PL/Tcl regression test to dodge a possible bug or zone dependency.
- 5b5b2fb4035d 9.2.21 landed
- dd2d437e8ee7 9.4.12 landed
- d27a48ad63f4 9.6.3 landed
- a8aeb871d914 9.5.7 landed
- 300ac7ff190f 9.3.17 landed
- 170511b30da4 10.0 landed