On Thu, Mar 25, 2010 at 11:56 PM, Eliot Gable
egable+pgsql-performa...@gmail.com wrote:
How many rows min/max/avg are coming back in your refcursors? Are you
using cursors in order to return multiple complex data structures
(sets, etc) in a single function call?
I think the largest number
On 26/03/10 03:56, Eliot Gable wrote:
I really am chasing milliseconds here, and I appreciate all your feedback.
You've given me a relatively large number of possible optimizations I can
try out. I will definitely try out the libpqtypes. That sounds like a
promising way to further cut down on
On Tue, Mar 23, 2010 at 5:00 PM, Eliot Gable
egable+pgsql-performa...@gmail.com wrote:
The complex type contains roughly 25 fields, mostly text, plus another 10
REFCURSORs.
How many rows min/max/avg are coming back in your refcursors? Are you
using cursors in order to return multiple complex
On Thu, Mar 25, 2010 at 10:00 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Tue, Mar 23, 2010 at 5:00 PM, Eliot Gable
egable+pgsql-performa...@gmail.com egable%2bpgsql-performa...@gmail.com
wrote:
The complex type contains roughly 25 fields, mostly text, plus another 10
REFCURSORs.
How
I would greatly appreciate any advice anyone could give me in terms of
performance tuning a large PL/PGSQL stored procedure. First, I should point
out that I have read a considerable amount of information in the online
PostgreSQL documentation and on Google about optimizing SQL queries and
