pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: rjhb@bb-c.de
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18581: psql symbol append_history not found when quitting
Date: Tue, 13 Aug 2024 14:23:25 -0400
Message-ID: <47695.1723573405@sss.pgh.pa.us> (raw)
In-Reply-To: <18581-21ea8faa9008ac68@postgresql.org>
References: <18581-21ea8faa9008ac68@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> writes:
> When leaving a psql session via \q in 15.8 (which I built today under Oracle
> Solaris 11.4), I get:
>  ld.so.1: psql: fatal: relocation error: file
> /opt/postgres/15-pgdg/bin/64/psql: symbol append_history: referenced symbol
> not found
> Killed

Hmmm...

> Isn't the a "pg_" missing on line 462?

No.  That's intending to call the readline function append_history.
That call has been there since 2009.  I'm not sure what changed
between your 15.6 and 15.8 builds, but that wasn't it.

However, that call is only compiled if HAVE_APPEND_HISTORY is
defined, which indicates that configure successfully probed
for existence of the function.  Maybe you need to take a closer
look at what configure did?

			regards, tom lane





view thread (3+ messages)  latest in thread

Message-ID: <47695.1723573405@sss.pgh.pa.us>
Permalink:  ../47695.1723573405@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/47695.1723573405@sss.pgh.pa.us

 · 

reply

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-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, rjhb@bb-c.de, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18581: psql symbol append_history not found when quitting
  In-Reply-To: <47695.1723573405@sss.pgh.pa.us>

* 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