From: Stephen Frost <sfrost@snowman.net>
To: Florian Weimer <fweimer@bfk.de>
Cc: Guoping Zhang <guoping.zhang@nec.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
Date: Wed, 19 Jul 2006 10:26:43 -0400
Message-ID: <20060719142643.GF20016@kenobi.snowman.net> (raw)
In-Reply-To: <82bqrl1xwk.fsf@mid.bfk.de>
References: <82irlu2jk9.fsf@mid.bfk.de>
<003501c6ab05$a4978f20$74304c93@eddy>
<20060719140135.GE20016@kenobi.snowman.net>
<82bqrl1xwk.fsf@mid.bfk.de>
* 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
Attachments:
signature.asc (application/pgp-signature, 188B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sfrost@snowman.net, fweimer@bfk.de, guoping.zhang@nec.com.au
Subject: Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
In-Reply-To: <20060719142643.GF20016@kenobi.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox