Re: libpq: PQgetCopyData() and allocation overhead - Mailing list pgsql-hackers

From Jelte Fennema
Subject Re: libpq: PQgetCopyData() and allocation overhead
Date
Msg-id CAGECzQR98cz9BnydSdPn91pMTJRJ41OhPM9+eYst3dpp-0zwdw@mail.gmail.com
Whole thread Raw
In response to Re: libpq: PQgetCopyData() and allocation overhead  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: libpq: PQgetCopyData() and allocation overhead  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 3 Mar 2023 at 17:33, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> If you mean exposing PQExpBuffer to users of libpq-fe.h, I'd be very
> seriously against that.  I realize that libpq exposes it at an ABI
> level, but that doesn't mean we want non-Postgres code to use it.

The code comment in the pqexpbuffer.h header suggests that client
applications are fine too use the API to:

> * This module is essentially the same as the backend's StringInfo data type,
> * but it is intended for use in frontend libpq and client applications.

I know both pg_auto_failover and pgcopydb use it quite a lot.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Harden new test case against force_parallel_mode = regress.
Next
From: Robert Haas
Date:
Subject: Re: Fix comments in gistxlogDelete, xl_heap_freeze_page and xl_btree_delete