Re: Deleting prepared statements from libpq. - Mailing list pgsql-hackers

From jian he
Subject Re: Deleting prepared statements from libpq.
Date
Msg-id CACJufxHpuKsfRKp-8TJr_=MeD6rA6+WZjWgCvmsRM3j+we1SOw@mail.gmail.com
Whole thread Raw
In response to Re: Deleting prepared statements from libpq.  (Jelte Fennema <me@jeltef.nl>)
Responses Re: Deleting prepared statements from libpq.
List pgsql-hackers
On Sun, Jun 18, 2023 at 7:04 PM Jelte Fennema <me@jeltef.nl> wrote:
>
> On Sat, 17 Jun 2023 at 15:34, jian he <jian.universality@gmail.com> wrote:
> > I failed to link it. I don't know why.
>
> Sorry about that. I attached a new patch that allows linking to the
> new functions (I forgot to add the functions to exports.txt). This new
> patch also adds some basic tests for these new functions.

previously I cannot link it. with
v2-0001-Support-sending-Close-messages-from-libpq.patch. now I can
compile it, link it, but then run time error.
same c program in the first email.
when I run it ./a.out, then error:
./a.out: symbol lookup error: ./a.out: undefined symbol: PQsendClosePrepared



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Refactoring backend fork+exec code
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] hstore: Fix parsing on Mac OS X: isspace() is locale specific