From: Joe Conway <mail@joeconway.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Guoping Zhang <guoping.zhang@nec.com.au>
Cc: Florian Weimer <fweimer@bfk.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance penalty for remote access of postgresql
Date: Wed, 19 Jul 2006 08:49:17 -0700
Message-ID: <44BE547D.1000602@joeconway.com> (raw)
In-Reply-To: <20060719140135.GE20016@kenobi.snowman.net>
References: <82irlu2jk9.fsf@mid.bfk.de>
<003501c6ab05$a4978f20$74304c93@eddy>
<20060719140135.GE20016@kenobi.snowman.net>
Stephen Frost wrote:
> * Guoping Zhang (guoping.zhang@nec.com.au) wrote:
>
>>Obviously, if there is no better solution, the TCP round trip penalty will
>>stop us doing so as we do have performance requirement.
>
> Actually, can't you stick multiple inserts into a given 'statement'?
> ie: insert into abc (123); insert into abc (234);
>
> I'm not 100% sure if that solves the round-trip issue, but it might..
> Also, it looks like we might have multi-value insert support in 8.2 (I
> truely hope so anyway), so you could do something like this:
> insert into abc (123),(234);
Yeah, see my post from last night on PATCHES. Something like "insert
into abc (123); insert into abc (234); ..." actually seems to work
pretty well as long as you don't drive the machine into swapping. If
you're doing a very large number of INSERTs, break it up into bite-sized
chunks and you should be fine.
Joe
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: mail@joeconway.com, sfrost@snowman.net, guoping.zhang@nec.com.au, fweimer@bfk.de
Subject: Re: Performance penalty for remote access of postgresql
In-Reply-To: <44BE547D.1000602@joeconway.com>
* 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