Re: Exporting more function in libpq - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Exporting more function in libpq
Date
Msg-id CAMsr+YFmN-hdUrKCMZHvYQ_NxzPMQcbvFBMiuaVQnSnfArAn5Q@mail.gmail.com
Whole thread Raw
In response to Exporting more function in libpq  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: Exporting more function in libpq  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 19 August 2016 at 14:17, Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
I would like to proppse to export these functions in libpq.

pqPutMsgStart
pqPutMsgEnd
pqPutc
pqPuts
pqPutInt
pqPutnchar
pqFlush
pqHandleSendFailure

I think this would be useful to create a tool/library which needs to
handle frontend/backend protocol messages in detail.

Shouldn't that generally be done by extending libpq to add the required functionality?

If you're extending the server-side protocol and want to handle new message types, you're presumably able to extend libpq too. If you're not extending the server-side protocol, what is it that you want to do but cannot currently do with libpq? Is there a reaonable way to add that to libpq?

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Logical decoding restart problems
Next
From: Craig Ringer
Date:
Subject: Re: Most efficient way for libPQ .. PGresult serialization