Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance? - Mailing list pgsql-performance

From Stephen Frost
Subject Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
Date
Msg-id 20060719142643.GF20016@kenobi.snowman.net
Whole thread Raw
In response to Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?  (Florian Weimer <fweimer@bfk.de>)
List pgsql-performance
* Florian Weimer (fweimer@bfk.de) wrote:
> * Stephen Frost:
> > Actually, can't you stick multiple inserts into a given 'statement'?
> > ie: insert into abc (123); insert into abc (234);
>
> IIRC, this breaks with PQexecParams, which is the recommended method
> for executing SQL statements nowadays.

For prepared queries you're absolutely correct.  It's also true that
it's the recommended approach for large numbers of inserts.  If the
network delay is more of a problem than the processing speed then it
might make sense.

It does seem to me that with multi-value insert we might consider
changes to libpq to be able to use multi-value prepared inserts...  Or
it might be interesting to see the performance of non-prepared
multi-value inserts vs. prepared statements.

    Thanks,

        Stephen

Attachment

pgsql-performance by date:

Previous
From: Florian Weimer
Date:
Subject: Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
Next
From: Bill Moran
Date:
Subject: Re: Performance penalty for remote access of postgresql