Re: Exporting more function in libpq

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Exporting more function in libpq
Date: 2016-08-20 06:36:58
Message-ID: CAMsr+YFmN-hdUrKCMZHvYQ_NxzPMQcbvFBMiuaVQnSnfArAn5Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 19 August 2016 at 14:17, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-08-20 06:39:28 Re: Most efficient way for libPQ .. PGresult serialization
Previous Message Craig Ringer 2016-08-20 06:33:33 Re: Logical decoding restart problems