Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1)

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.

retards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company