2018-09-12 0:59 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > The implementation of PQresultMemsize is simple and correct.
>
> Hm, well, only for small values of "correct". A quick look at PQclear
> to see just what it clears shows that PGEvent objects associated with the
> PGresult were over
Pavel Stehule writes:
> The implementation of PQresultMemsize is simple and correct.
Hm, well, only for small values of "correct". A quick look at PQclear
to see just what it clears shows that PGEvent objects associated with the
PGresult were overlooked. While that's not hard to fix (and I did
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: not tested
Spec compliant: not tested
Documentation:tested, passed
The implementation of PQresultMemsize is simple and correct. There ar
Attached is an updated patch of PQresultMemsize(). The implementation is
unchanged, but I added SGML documentation about this new function.
I'd be pleased about comments to adding this to libpq.
--
Kind Regards,
Lars
From 766a7f2381ae6c9d442a7359cabc58515186f8c4 Mon Sep 17 00:00:00 2001
From: L
Hello,
I would like to be able to retrieve the size of memory internally
allocated by libpq for a result. The reason is that we have a Ruby
wrapper that exposes libpq in Ruby. The problem is that Ruby's GC
doesn't know how much memory has been allocated by libpq, so no pressure
is applied to the G
