Date: Wed, 3 Jun 2026 16:36:34 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: future of PQfn()
Message-ID: <aiCeYhW4Ksu-BFqC@nathan>
References: <ahXE28klgxIJXBLq@nathan>
 <CAOYmi+m3bKWfHhAj3iKBa3mKj=_4MO3xY2WpBsB4Hx7yyAE7rw@mail.gmail.com>
 <ahX6nb1aqh51IhHC@nathan>
 <CAOYmi+n6eFXs_pncObs9Vhe7S1gbvepRncYJaaO98anxL8WODg@mail.gmail.com>
 <ahmtVYcf4EYwz02U@nathan>
 <CAOYmi+mA4Cdb+RWV2M83FbsSN85t2iuoXejA-PKNrQ_ayHOQWw@mail.gmail.com>
 <ahm6kuL3L3wSYo6d@nathan>
 <CAOYmi+nhtqGZAgtLvR2OdNZ8mfdY79qseEtKXnbs1jvtLNOrZA@mail.gmail.com>
 <ahnB8zuR0AYegcJI@nathan>
 <CAOYmi+=sO6dR6P2c48f6ZT9aOgzVdf+pjn3TMsehTPr8-Yxjsw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="6CoALBM/+cswbGQ8"
Content-Disposition: inline
In-Reply-To: 
 <CAOYmi+=sO6dR6P2c48f6ZT9aOgzVdf+pjn3TMsehTPr8-Yxjsw@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/aiCeYhW4Ksu-BFqC%40nathan>
Precedence: bulk


--6CoALBM/+cswbGQ8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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

--6CoALBM/+cswbGQ8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=v3-0001-remove-PQfn.patch