From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1)
Date: Tue, 19 Sep 2023 21:40:46 +0200
Message-ID: <20f76b64-c572-7320-64cc-2f6fb3548552@enterprisedb.com> (raw)
In-Reply-To: <380389.1695141908@sss.pgh.pa.us>
References: <316d304a-1dcd-cea1-3d6c-27f794727a06@enterprisedb.com>
<220198.1695063151@sss.pgh.pa.us>
<595acc76-6b9c-1445-67e4-00c84cb1a4d8@enterprisedb.com>
<380389.1695141908@sss.pgh.pa.us>
On 9/19/23 18:45, Tom Lane wrote:
> Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
>> I have no experience with tcl, but I tried this in the two tclsh
>> versions installed no the system (8.6 and 8.7):
>
>> bsd@freebsd:~ $ tclsh8.7
>> % clock scan "1/26/2010"
>> time value too large/small to represent
>
>> bsd@freebsd:~ $ tclsh8.6
>> % clock scan "1/26/2010"
>> time value too large/small to represent
>
>> AFAIK this is what the tcl_date_week(2010,1,26) translates to.
>
> Oh, interesting. On my FreeBSD 13.1 arm64 system, it works:
>
> $ tclsh8.6
> % clock scan "1/26/2010"
> 1264482000
>
> I am now suspicious that there's some locale effect that we have
> not observed before (though why not?). What is the result of
> the "locale" command on your box? Mine gives
>
> $ locale
> LANG=C.UTF-8
> LC_CTYPE="C.UTF-8"
> LC_COLLATE="C.UTF-8"
> LC_TIME="C.UTF-8"
> LC_NUMERIC="C.UTF-8"
> LC_MONETARY="C.UTF-8"
> LC_MESSAGES="C.UTF-8"
> LC_ALL=
>
bsd@freebsd:~ $ locale
LANG=C.UTF-8
LC_CTYPE="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_TIME="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_ALL=
bsd@freebsd:~ $ tclsh8.6
% clock scan "1/26/2010"
time value too large/small to represent
However, I wonder if there's something wrong with tcl itself,
considering this:
% clock format 1360558800 -format %D
02/11/2013
% clock scan 02/11/2013 -format %D
time value too large/small to represent
That's a bit strange - it seems tcl can format a timestamp, but then
can't read it back in for some reason ...
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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: tomas.vondra@enterprisedb.com, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1)
In-Reply-To: <20f76b64-c572-7320-64cc-2f6fb3548552@enterprisedb.com>
* 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