pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Larry Rosenman <ler@lerctr.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: John Naylor <john.naylor@enterprisedb.com>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix out-of-bounds read in json_lex_string
Date: Tue, 12 Jul 2022 10:29:20 -0500
Message-ID: <a549ae1ed58756d2b5c6a6f1bfe636cb@lerctr.org> (raw)
In-Reply-To: <1403493.1657606036@sss.pgh.pa.us>
References: <E1oB7Us-002Nic-BI@gemulon.postgresql.org>
	<CAFBsxsGTPnDRbwW0DR0mDKGATVD26rO4hdn_-b2Hq=7dv=siYw@mail.gmail.com>
	<1401975.1657605607@sss.pgh.pa.us>
	<1403493.1657606036@sss.pgh.pa.us>

On 07/12/2022 1:07 am, Tom Lane wrote:
> I wrote:
>> John Naylor <john.naylor@enterprisedb.com> writes:
>>> ld: error: unable to find library -lldap_r
> 
>> Agreed, that looks like some unrelated platform change.  Larry?
> 
> Upon further thought, this looks like fallout from an upgrade to
> OpenLDAP 2.5, which eliminated libldap_r.  That should be fine,
> but you might need to blow away the animal's accache files to
> make configure reconsider the situation.
> 
> 			regards, tom lane

I've killed the accache and ccache files, and it's flipped back to OK.
Yes, ports deprecated/removed openldap24 and replaced it with 
openldap26, and the host got
updated last night.
Sorry for the grief :)

-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106





view thread (5+ messages)

Message-ID: <a549ae1ed58756d2b5c6a6f1bfe636cb@lerctr.org>
Permalink:  ../a549ae1ed58756d2b5c6a6f1bfe636cb@lerctr.org/
Also on:    postgresql.org/message-id/a549ae1ed58756d2b5c6a6f1bfe636cb@lerctr.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: ler@lerctr.org, tgl@sss.pgh.pa.us, john.naylor@enterprisedb.com
  Subject: Re: pgsql: Fix out-of-bounds read in json_lex_string
  In-Reply-To: <a549ae1ed58756d2b5c6a6f1bfe636cb@lerctr.org>
  References: <E1oB7Us-002Nic-BI@gemulon.postgresql.org> <CAFBsxsGTPnDRbwW0DR0mDKGATVD26rO4hdn_-b2Hq=7dv=siYw@mail.gmail.com> <1401975.1657605607@sss.pgh.pa.us> <1403493.1657606036@sss.pgh.pa.us> <a549ae1ed58756d2b5c6a6f1bfe636cb@lerctr.org>

* 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