Skip site navigation (1) Skip section navigation (2)

Re: performance for high-volume log insertion

From: david(at)lang(dot)hm
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-performance(at)postgresql(dot)org
Subject: Re: performance for high-volume log insertion
Date: 2009-04-27 07:14:38
Message-ID: alpine.DEB.1.10.0904270012460.16008@asgard.lang.hm (view raw or flat)
Thread:
Lists: pgsql-performance
On Sun, 26 Apr 2009, Kris Jurka wrote:

> Scott Marlowe wrote:
>> On Sun, Apr 26, 2009 at 11:07 AM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>>> 
>>> As a note for non-JDBC users, the JDBC driver's batch interface allows
>>> executing multiple statements in a single network roundtrip.  This is
>>> something you can't get in libpq, so beware of this for comparison's 
>>> sake..
>> 
>> Really?  I thought that executing statements like so:
>> 
>> select * from a;insert ...;delete;
>> 
>> in psql / libpq would execute them all in one trip.
>
> Right, but those aren't prepared.  I suppose it's possible to issue a prepare 
> and then issue a batch of comma separated "execute" statements, but that's 
> not exactly a natural interface.

for the task we are discussing here (log inserting) why wouldn't it be 
reasonable to have a prepared insert and then do begin;execute...;end to 
do a batch of them at once.

David Lang

In response to

pgsql-performance by date

Next:From: WojtekDate: 2009-04-27 09:39:38
Subject: plpgsql function running long, but resources consumption is very low
Previous:From: Scott MarloweDate: 2009-04-27 07:07:03
Subject: Re: performance for high-volume log insertion

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group