From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christoph Berg <myon(at)debian(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pl/perl extension fails on Windows |
Date: | 2017-07-30 21:30:39 |
Message-ID: | 10328.1501450239@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christoph Berg <myon(at)debian(dot)org> writes:
> Re: Tom Lane 2017-07-28 <3254(dot)1501276475(at)sss(dot)pgh(dot)pa(dot)us>
>> Christoph Berg <myon(at)debian(dot)org> writes:
>>> The plperl segfault on Debian's kfreebsd port I reported back in 2013
>>> is also still present:
>> So it'd be interesting to know if it's any better with HEAD ...
> Unfortunately not:
> The only interesting line in log/postmaster.log is a log_line_prefix-less
> Util.c: loadable library and perl binaries are mismatched (got handshake key 0xd500080, needed 0xd600080)
> ... which is unchanged from the beta2 output.
Well, that's quite interesting, because it implies that this is indeed
the same type of problem. I wonder why the patch didn't fix it?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Shay Rojansky | 2017-07-30 22:15:09 | Re: PostgreSQL not setting OpenSSL session id context? |
Previous Message | Christoph Berg | 2017-07-30 21:14:44 | Re: pl/perl extension fails on Windows |