Re: future of PQfn()

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: future of PQfn()
Date: 2026-06-03 21:36:34
Message-ID: aiCeYhW4Ksu-BFqC@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

While the prepared statement deallocation idea bakes in the other thread, I
thought I'd post a new patch set here. I've reordered things a bit and
left out the conversion to prepared statements for now (although I do have
a patch for that). 0001 removes PQfn() and changes all internal uses to
PQnfn(). 0002 and 0003 are just some additional cleanup that I noticed
as I've been working on this stuff.

--
nathan

Attachment Content-Type Size
v3-0001-remove-PQfn.patch text/plain 13.1 KB
v3-0002-remove-lo_hton64-and-lo_ntoh64.patch text/plain 2.6 KB
v3-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
Previous Message Tom Lane 2026-06-03 21:27:22 Re: Centralised architecture detection