From: Devrim Gündüz <devrim@gunduz.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: drop support for Python 2.3
Date: Sun, 19 Feb 2017 23:10:29 +0300
Message-ID: <1487535029.3796.1.camel@gunduz.org> (raw)
In-Reply-To: <24334.1487530091@sss.pgh.pa.us>
References: <7d5073f6-d9ea-ab09-4805-69a12f23e52f@2ndquadrant.com>
<9516.1486529343@sss.pgh.pa.us>
<adb38a71-0aa7-087d-2791-4987f3026244@2ndquadrant.com>
<1486568115.5462.50.camel@gunduz.org>
<0e2fd256-0a3a-bae8-4ef2-c536139c64cb@2ndquadrant.com>
<1487493740.2748.13.camel@gunduz.org>
<797.1487517822@sss.pgh.pa.us>
<1453.1487518921@sss.pgh.pa.us>
<1487527748.2748.37.camel@gunduz.org>
<24334.1487530091@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Hi Tom,
On Sun, 2017-02-19 at 13:48 -0500, Tom Lane wrote:
> 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?
Just downloaded SRPM, and I don't *think* so their patch would break this.
> Or conceivably it's timezone dependent?
FWIW, the timezone of the server is GMT+3, if that is what you are asking.
> 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?
Yes, I got 04.
Regards,
--
Devrim Gündüz
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachments:
[application/pgp-signature] signature.asc (818B, ../1487535029.3796.1.camel@gunduz.org/2-signature.asc)
download
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-hackers@postgresql.org
Cc: devrim@gunduz.org, tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com
Subject: Re: drop support for Python 2.3
In-Reply-To: <1487535029.3796.1.camel@gunduz.org>
* 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