Received: from dv.kp.dlr.de (dv.kp.dlr.de [129.247.97.1]) by hub.org (8.10.1/8.10.1) with ESMTP id e7I83pm89189 for ; Fri, 18 Aug 2000 04:03:51 -0400 (EDT) Received: from sea-gw.sea.com (yyy.kp.dlr.de [129.247.113.223]) by dv.kp.dlr.de (8.10.1/8.10.1) with ESMTP id e7I83nU132698; Fri, 18 Aug 2000 10:03:49 +0200 Received: from joebox.sea-gmbh.com (joebox.sea.com [192.168.0.20]) by sea-gw.sea.com (8.7.4/8.7.1) with ESMTP id KAA18761; Fri, 18 Aug 2000 10:03:48 +0200 Message-Id: <4.3.2.7.0.20000818100053.00ae53b0@192.168.0.1> X-Sender: joe@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 18 Aug 2000 10:03:48 +0200 To: Webb Sprague From: Joerg Hessdoerfer Subject: Re: Continuous inserts... Cc: pgsql-sql@postgresql.org In-Reply-To: <20000817183802.19885.qmail@web804.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200008/170 hi! At 11:38 17.08.00 -0700, you wrote: >Hi All. > >Shouldn't Postgres block while vacuuming, and then >continue inserting starting where it left off? Is the >time lag too much? For me - yes. My app can accept some hundredes of ms time lag - not seconds or, like with a VACUUM, minutes (I've seen it taking hours, but that was a _LARGE_ table on 6.5.x). >I am curious because I am going to build a similar app >soon, basically parsing and inserting log file >entries. Rules do the trick - insert into a second table unnoticed by the inserter client. See my previous posting for slightly more detail. Greetings, Joerg +------**** Science & Engineering Applications GmbH ****------+ | | | Joerg Hessdoerfer | | Leading SW developer Phone: +49 (0)2203-962211 | | S.E.A GmbH Fax: -962212 | | D-51147 Koeln Internet: joerg.hessdoerfer@sea-gmbh.com | | http://www.sea-gmbh.com | +---------------------------------------------------------------+