Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-06 Thread Justin Pryzby
On Sun, Oct 06, 2019 at 05:57:38PM +0200, Christoph Zwerschke wrote: > Am 06.10.2019 um 15:20 schrieb Justin Pryzby: > > Remember, lazy binding is the default on my machine, and my patch > > doesn't DWIW here.. So I don't think adding lazy link options > > is going to help. I think because of

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-06 Thread Christoph Zwerschke
Am 06.10.2019 um 15:20 schrieb Justin Pryzby: > Remember, lazy binding is the default on my machine, and my patch > doesn't DWIW here.. So I don't think adding lazy link options > is going to help. I think because of something python is doing (??) Another difference is that in your example

[PyGreSQL] PyGreSQL #84: Consistent handling of optional functionality

2019-10-06 Thread PyGreSQL issue tracker
#84: Consistent handling of optional functionality --+- Reporter: cito | Owner: Type: defect| Status: new Priority: major | Milestone: 5.2 Component: C Module |Version: 5.0 Keywords:|

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-06 Thread Justin Pryzby
On Sun, Oct 06, 2019 at 01:03:21PM +0200, Christoph Zwerschke wrote: > Am 06.10.2019 um 01:15 schrieb Justin Pryzby: > >On Sat, Oct 05, 2019 at 11:43:23PM +0200, Christoph Zwerschke wrote: > >..but I don't think it's a solution for pygres ? I tried it and still get a > >symbol resolution error.

Re: [PyGreSQL] [PATCH] PQresultMemorySize

2019-10-06 Thread Christoph Zwerschke
Am 06.10.2019 um 01:15 schrieb Justin Pryzby: On Sat, Oct 05, 2019 at 11:43:23PM +0200, Christoph Zwerschke wrote: ..but I don't think it's a solution for pygres ? I tried it and still get a symbol resolution error. So, unless someone knows or finds better, it means there's nothing stopping