Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org
	(8.8.8/8.7.5) with ESMTP id LAA06280 for
	<pgsql-interfaces@postgreSQL.org>;
	Fri, 17 Jul 1998 11:48:07 -0400 (EDT)
Received: from insightdist.com (nobody@localhost)
	by u1.abs.net (8.9.0/8.9.0) with UUCP id LAA02804
	for pgsql-interfaces@postgreSQL.org;
	Fri, 17 Jul 1998 11:28:57 -0400 (EDT)
X-Authentication-Warning: u1.abs.net: nobody set sender to
	insightdist.com!daveh using -f
Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03)
	id AA20403; Fri, 17 Jul 1998 11:13:52 -0400
Received: from daveh by ceodev (AIX 4.1/UCB 5.64/4.03)
	id AA51564; Fri, 17 Jul 1998 11:13:52 -0400
Message-Id: <35AF6B60.742B4C46@insightdist.com>
Date: Fri, 17 Jul 1998 11:18:56 -0400
From: David Hartwig <daveh@insightdist.com>
Organization: Insight Distribution Systems
X-Mailer: Mozilla 4.05 [en] (Win95; I)
Mime-Version: 1.0
To: Cyril Ferrand <Cyril.Ferrand@sophia.inria.fr>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] perl interface
References: <199807171232.OAA17315@celia.inria.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Cyril Ferrand wrote:

> Hello
>         Is there someone who use perl interface to postgres to put a lot of data into
> a base.
> When my table are 40 meg my perl stop...
>

I'll take a good guess based on what little information you have provided.   I will
assume the you ran a query which requested a large chunk of that 40 meg table.   The perl
interface uses libpq.  And libpq slurps the entire query result into memory before
passing control back to the users code.   This is a weakness of this library.  May I
suggest that you declare a cursor and request the data in chunks. (fetch 100 rows at a
time)   If you use a cursor and fetch only one row at a time you may be disappointed in
the performance.