Postgres Pro
Downloads
Home   >   mailing lists

Re: Running PostgreSQL as fast as possible no matter the consequences - Mailing list pgsql-performance

From Dimitri Fontaine
Subject Re: Running PostgreSQL as fast as possible no matter the consequences
Date
Msg-id m2mxpj6c6d.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Running PostgreSQL as fast as possible no matter the consequences  ("Lello, Nick" <nick.lello@rentrakmail.com>)
List pgsql-performance
Tree view 
"Lello, Nick" <nick.lello@rentrakmail.com> writes:
> A bigger gain can probably be had if you have a tightly controlled
> suite of queries that will be run against the database and you can
> spend the time to tune each to ensure it performs no sequential scans
> (ie: Every query uses index lookups).

Given a fixed pool of queries, you can prepare them in advance so that
you don't usually pay the parsing and planning costs. I've found that
the planning is easily more expensive than the executing when all data
fits in RAM.

Enter pgbouncer and preprepare :
  http://wiki.postgresql.org/wiki/PgBouncer
  http://preprepare.projects.postgresql.org/README.html

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

pgsql-performance by date:

Previous
From: "Pierre C"
Date:
Subject: Re: Select * is very slow
Next
From: Klaus Ita
Date:
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences