Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Justin Pryzby
On Sat, Oct 05, 2019 at 11:43:23PM +0200, Christoph Zwerschke wrote: > Am 05.10.2019 um 23:10 schrieb Christoph Zwerschke: > >Just tried what you did with that t.c program, but strangely I get the > >"undefined symbol" error when I downgrade libpq and run "./t 0", even when > >LD_BIND_NOW is not

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Christoph Zwerschke
Am 05.10.2019 um 23:33 schrieb Justin Pryzby: > You probably realized that my email failed to show that I > downgraded libpq between invocacations of "PGDATABASE=postgres ./t 1" Yes, I understood what you were doing. But I could only reproduce it when adding the "-Wl,-z,lazy" option. Not sure

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Christoph Zwerschke
Am 05.10.2019 um 23:10 schrieb Christoph Zwerschke: Just tried what you did with that t.c program, but strangely I get the "undefined symbol" error when I downgrade libpq and run "./t 0", even when LD_BIND_NOW is not defined. I am using Ubuntu instead of Debian, but that shouldn't matter.

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Justin Pryzby
On Sat, Oct 05, 2019 at 07:47:50PM +0200, Christoph Zwerschke wrote: > > Am 05.10.2019 um 18:47 schrieb Justin Pryzby: > > On Sat, Oct 05, 2019 at 06:37:36PM +0200, Christoph Zwerschke wrote: > >> Are you sure you compiled that with the pgconfig.h of Postgres 12? > >> setup.py is using the

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Christoph Zwerschke
Am 05.10.2019 um 18:47 schrieb Justin Pryzby: > On Sat, Oct 05, 2019 at 06:37:36PM +0200, Christoph Zwerschke wrote: >> Are you sure you compiled that with the pgconfig.h of Postgres 12? >> setup.py is using the includes specified by the pgconfig tool. > The intended behavior is to hit the

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Christoph Zwerschke
Am 05.10.2019 um 18:04 schrieb Justin Pryzby: On Sat, Oct 05, 2019 at 04:48:40PM +0200, Christoph Zwerschke wrote: Find attached minimal patch. Thank you, looks fine. I've already added docs and tests as well, but not yet committed to trunk. I didn't mean you had to stop and do that - I

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Justin Pryzby
On Sat, Oct 05, 2019 at 04:48:40PM +0200, Christoph Zwerschke wrote: > >Find attached minimal patch. > > Thank you, looks fine. I've already added docs and tests as well, but not > yet committed to trunk. I didn't mean you had to stop and do that - I hammered it out while waiting for

[PyGreSQL] [1027] trunk: Consistent spelling of PyGreSQL

2019-10-05 Thread NULL
Title: [1027] trunk: Consistent spelling of PyGreSQL Revision 1027 Author cito Date 2019-10-05 11:30:59 -0400 (Sat, 05 Oct 2019) Log Message Consistent spelling of PyGreSQL Modified Paths trunk/docs/download/files.rst trunk/pgdb.py trunk/setup.py Diff Modified:

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-05 Thread Christoph Zwerschke
Am 05.10.2019 um 02:07 schrieb Justin Pryzby: On Wed, May 15, 2019 at 08:44:49AM -0500, Justin Pryzby wrote: Also, as of PG12 (unreleased), there'll be this new interface: https://www.postgresql.org/docs/devel/release-12.html#id-1.3.7 |Add libpq function to report the memory size of the query