Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted()

2019-04-20 Thread PyGreSQL issue tracker
#77: Bad performance of query_formatted() ---+- Reporter: justin| Owner: cito Type: task | Status: closed Priority: major | Milestone: 5.1 Component: DB API 2 |Version: 5.0 Resolution: fixed |

Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted()

2019-04-20 Thread Christoph Zwerschke
Am 20.04.2019 um 01:20 schrieb Justin Pryzby: Also, caching the types of the values works only if you have very few different values (like in your case only a zero), but for most real-world examples with different strings or floats this will not work. Do you mean "..works only if you

Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted()

2019-04-19 Thread Justin Pryzby
Thanks for looking at this On Fri, Apr 19, 2019 at 09:46:18PM -, PyGreSQL issue tracker wrote: > But I think the huge performance difference in your example is only an > artifact of the special kind of query you were using, with very simple > values (just integer zeroes) and many columns.

Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted()

2019-04-18 Thread PyGreSQL issue tracker
#77: Bad performance of query_formatted() ---+- Reporter: justin| Owner: cito Type: task | Status: new Priority: major | Milestone: 5.1 Component: DB API 2 |Version: 5.0 Resolution:|

Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted()

2019-04-18 Thread PyGreSQL issue tracker
#77: Bad performance of query_formatted() ---+- Reporter: justin| Owner: cito Type: task | Status: new Priority: major | Milestone: 5.1 Component: DB API 2 |Version: 5.0 Resolution:|