Re: future of PQfn()

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: future of PQfn()
Date: 2026-06-04 14:57:47
Message-ID: aiGSa7XpUTRFt-be@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 04, 2026 at 11:39:02AM +0100, Dagfinn Ilmari Mannsåker wrote:
> Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
>
>> - <sect1 id="libpq-fastpath">
>> - <title>The Fast-Path Interface</title>
>> -
>> - <indexterm zone="libpq-fastpath">
>> - <primary>fast path</primary>
>> - </indexterm>
>
> Should we move this to the "Obsolete or Renamed Features" appendix
> (e.g. appendix-obsolete-libpq-fastpath.sgml) with a description of why
> it was removed?

Yes, I think we should. Done in the attached.

--
nathan

Attachment Content-Type Size
v4-0001-remove-PQfn.patch text/plain 15.4 KB
v4-0002-remove-lo_hton64-and-lo_ntoh64.patch text/plain 2.6 KB
v4-0003-add-helper-functions-for-fast-path-arg-setup.patch text/plain 6.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-06-04 15:04:31 Re: (SQL/PGQ) cache lookup failed for label
Previous Message Hans Buschmann 2026-06-04 14:42:18 PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c