Re: High end server and storage for a PostgreSQL OLTP system - Mailing list pgsql-performance

From Cosimo Streppone
Subject Re: High end server and storage for a PostgreSQL OLTP system
Date
Msg-id 420141A8.2090800@streppone.it
Whole thread Raw
In response to Re: High end server and storage for a PostgreSQL OLTP system  ("Merlin Moncure" <merlin.moncure@rcsonline.com>)
Responses Re: High end server and storage for a PostgreSQL OLTP system  (Cosimo Streppone <cosimo@streppone.it>)
List pgsql-performance
Merlin Moncure wrote:

> > [...]
 > > (...DBI + DBD::Pg), so that switching to 8.0 should
> > automatically enable the "single-prepare, multiple-execute" behavior,
> > saving a lot of query planner processing, if I understand correctly.
>
> [...]
>
> I know that the perl people were pushing for certain features into the
> libpq library (describing prepared statements, IIRC).  I think this
> stuff made it into 8.0...have no clue about DBD::pg.

For the record: yes, DBD::Pg in CVS (> 1.32) has support
for server prepared statements.

> If everything is working the way it's supposed to, 8.0 should be faster
> than 7.1 (like, twice faster) for what you are probably trying to do.

In the next days I will be testing the entire application with the
same database only changing the backend from 7.1 to 8.0, so this is
a somewhat perfect condition to have a "real-world" benchmark
of Pg 8.0 vs 7.1.x performances.

--
Cosimo


pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: horizontal partition
Next
From: Daniel Ceregatti
Date:
Subject: Re: Bitmap indexes