> So, I embarked (yesterday) on a weekend project to add a new
> feature to Postgres...
> I use PHP with persistent connections and always have been
> bothered that those very small AJAX queries (usually simple selects
> returning 1 row) take more CPU in postgres to parse & plan than to
> actually execute.
Microsoft's answer to this issue with SQLServer appears to have been to
introduce a smart
cache for all statement plans. It seems to be very effective. I guess
you're doing much the
same thing but with more user intervention, in effect.
Are you sure that you application wouldn't benefit more from a MOM
persisted database connections? Have you looked at
In response to
pgsql-hackers by date
|Next:||From: Gokulakannan Somasundaram||Date: 2008-03-30 10:32:11|
|Subject: Re: Hash Join Optimization|
|Previous:||From: PFC||Date: 2008-03-30 07:16:34|
|Subject: first time hacker ;) messing with prepared statements|