Re: [postgis-users] Severe performance problems with prepared statements

2014-01-07 Thread Andy Colson
On 1/7/2014 3:04 PM, William Becker wrote: It looks like a bunch of row estimates are off. Have you run analyze on the db? Yeah - I did do that, or at least Vacuum analyzes. Running an analyze now: INFO: analyzing "public.place" INFO: "place": scanned 4134 of 4134 pages, containing 44228

Re: [postgis-users] Severe performance problems with prepared statements

2014-01-07 Thread William Becker
>It looks like a bunch of row estimates are off. Have you run analyze on the db? Yeah - I did do that, or at least Vacuum analyzes. Running an analyze now: INFO: analyzing "public.place" INFO: "place": scanned 4134 of 4134 pages, containing 442283 live rows and 0 dead rows; 3 rows in samp

Re: [postgis-users] Severe performance problems with prepared statements

2014-01-05 Thread Andy Colson
On 01/05/2014 11:12 AM, William Becker wrote: I just tried changing my code base from using hard coded queries to prepared statements. As part of this I pass a parameter as the argument to the ST_GeographyFromText() function. You can see the code here (1). After doing this, it took ~20 seconds

[postgis-users] Severe performance problems with prepared statements

2014-01-05 Thread William Becker
I just tried changing my code base from using hard coded queries to prepared statements. As part of this I pass a parameter as the argument to the ST_GeographyFromText() function. You can see the code here (1). After doing this, it took ~20 seconds to run, when previously it took ~2 seconds. I tho