Re: PG buildfarm member cisticola

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: huchangqi(at)loongson(dot)cn, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PG buildfarm member cisticola
Date: 2024-07-25 08:38:07
Message-ID: ZqIO76m9Svk1C-Ra@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 24, 2024 at 01:09:22PM +0200, Alvaro Herrera wrote:
> Hmm, it appears that these symbols did not exist in 1.1.1g, and since
> neither of them is invoked directly by the Postgres code, maybe the
> reason for this is that the OpenSSL headers being used do not correspond
> to the library being linked.

I am as puzzled as you are. The version of OpenSSL detected by
./configure is the same before and after the first failure. Well,
that's the output of `openssl` so perhaps we are just being lied here
and that we are trying to link to a different version in the
background. Impossible to say without more input from the machine
owner.

The two commits between the last success and the first failure are:
7e187a7386 Mon Jul 22 02:29:21 2024 UTC Fix unstable test in select_parallel.sql
2d8ef5e24f Mon Jul 22 00:28:01 2024 UTC Add new error code for "file name too long"

Discarding the first one points to the second, still I don't see a
relation, which would come down to a conflict with the new
ERRCODE_FILE_NAME_TOO_LONG (?).
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-07-25 08:55:19 Re: REINDEX not updating partition progress
Previous Message Jelte Fennema-Nio 2024-07-25 08:30:09 Re: Support prepared statement invalidation when result types change