Re: High end server and storage for a PostgreSQL OLTP system

From: Cosimo Streppone <cosimo(at)streppone(dot)it>
To: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>
Cc: Postgresql Performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: High end server and storage for a PostgreSQL OLTP system
Date: 2005-02-02 21:10:00
Message-ID: 420141A8.2090800@streppone.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Daniel Ceregatti 2005-02-02 23:18:37 Re: Bitmap indexes
Previous Message Josh Berkus 2005-02-02 20:09:06 Re: horizontal partition