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