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: Wed, 20 Sep 2023 20:09:53 +0200
Message-ID: <9ff0a03a-db64-dbab-3896-10c19ff009ce@enterprisedb.com> (raw)
In-Reply-To: <4ecba72e-4d58-20a9-bb7c-1a1b6b4f48b1@enterprisedb.com>
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>
<20f76b64-c572-7320-64cc-2f6fb3548552@enterprisedb.com>
<425660.1695165890@sss.pgh.pa.us>
<4ecba72e-4d58-20a9-bb7c-1a1b6b4f48b1@enterprisedb.com>
On 9/20/23 19:59, Tomas Vondra wrote:
>
>
> On 9/20/23 01:24, Tom Lane wrote:
>> Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
>>> bsd@freebsd:~ $ tclsh8.6
>>> % clock scan "1/26/2010"
>>> time value too large/small to represent
>>
>> In hopes of replicating this, I tried installing FreeBSD 14-BETA2
>> aarch64 on my Pi 3B. This test case works fine:
>>
>> $ tclsh8.6
>> % clock scan "1/26/2010"
>> 1264482000
>>
>> $ tclsh8.7
>> % clock scan "1/26/2010"
>> 1264482000
>>
>> and unsurprisingly, pltcl's regression tests pass. I surmise
>> that something is broken in BETA1 that they fixed in BETA2.
>>
>> plpython works too, with the python 3.9 package (and no older
>> python).
>>
>> However, all is not peachy, because plperl doesn't work.
>> Trying to CREATE EXTENSION either plperl or plperlu leads
>> to a libperl panic:
>>
>> pl_regression=# create extension plperl;
>> server closed the connection unexpectedly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>> The connection to the server was lost. Attempting reset: Succeeded.
>>
>> with this in the postmaster log:
>>
>> panic: pthread_key_create failed
>>
>> That message is certainly not ours, so it must be coming out of libperl.
>>
>> Another thing that seemed strange is that ecpg's preproc.o takes
>> O(forever) to compile. I killed the build after observing that the
>> compiler had gotten to 40 minutes of CPU time, and redid that step
>> with PROFILE=-O0, which allowed it to compile in 20 seconds or so.
>> (I also tried -O1, but gave up after a few minutes.) This machine
>> can compile the main backend grammar in a minute or two, so there is
>> something very odd there.
>>
>> I'm coming to the conclusion that 14-BETA is, well, beta grade.
>> I'll be interested to see if you get the same results when you
>> update to BETA2.
>
> Thanks, I'll try that when I'll be at the office next week.
>
FWIW when I disabled tcl, the tests pass (it's running with --nostatus
--nosend, so it's not visible on the buildfarm site). Including the
plperl stuff:
============== running regression test queries ==============
test plperl ... ok 397 ms
test plperl_lc ... ok 152 ms
test plperl_trigger ... ok 374 ms
test plperl_shared ... ok 163 ms
test plperl_elog ... ok 184 ms
test plperl_util ... ok 210 ms
test plperl_init ... ok 150 ms
test plperlu ... ok 117 ms
test plperl_array ... ok 228 ms
test plperl_call ... ok 189 ms
test plperl_transaction ... ok 412 ms
test plperl_plperlu ... ok 238 ms
======================
All 12 tests passed.
======================
I wonder if this got broken between BETA1 and BETA2.
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: <9ff0a03a-db64-dbab-3896-10c19ff009ce@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