Re: Exporting more function in libpq

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Exporting more function in libpq
Date: 2016-08-22 18:49:32
Message-ID: 20160822184932.GA146731@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Craig Ringer wrote:
> 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?

The thought that came to me was that maybe we need a separate library
that handles the lower level operations (a "fe/be" library, if you will)
which can be exported for others to use and is used by libpq to
implement the slightly-higher-level functionality.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-08-22 19:01:01 Re: Changed SRF in targetlist handling
Previous Message Andres Freund 2016-08-22 18:44:17 Re: Changed SRF in targetlist handling