On Tue, Jul 22, 2008 at 12:43 AM, Pavel Stehule <[EMAIL PROTECTED]> wrote: > 2008/7/20 Milan Oparnica <[EMAIL PROTECTED]>: >> Is it solved in MySQL or they've just tried ? > > http://www.mysqlperformanceblog.com/2006/08/02/mysql-prepared-statements/
Wow, the discussion at the bottom of that page made me really think. In MySQL you rely on the statement cache to provide data really fast without worrying too much about transactional semantics. In PostgreSQL you set up a set of 1 or more slony machines to act as cache / increase parallel performance. Or just throw more CPU and memory at it along with memcached. Or both. -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
