Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA04323; Wed, 9 Jun 93 22:41:49 -0700
Date: Wed, 9 Jun 93 22:41:49 -0700
Message-Id: <9306100541.AA04323@postgres.Berkeley.EDU>
From: ruby!imram@colossus.apple.com (Steve Davidson)
Subject: 1000 appends (This should not be cut off)
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu


The other meesages may have been cut off by mailers because
I put dots '.' in column 1.  This should have been okay but
several people complained.  Here's the bug report in full
glory.




I attempted to append 10000 records/tuples to a Postgres
database.  After 2098 appends I get the following error:
 
append CLIENT (id_client=1,name="aaa",city="XX")
  .
  .
  .
append CLIENT (id_client=2096,name="dcp",city="XX")
append CLIENT (id_client=2097,name="dcq",city="XX")
append CLIENT (id_client=2098,name="dcr",city="XX")
 
Error: No response from the backend, exiting...
 
 
 
 
The code to do the appends was a tight loop in perl:
 
 
    $name = 'aaa' ;
    &PQexec ("begin");
    for ($i = 1; $i <= 10000; $i++) {
        $query = " append CLIENT (id_client=$i,name=\"$name\",city=\"XX\") " ;
        &PQexec($query) ;
        $name++ ;
    }
    &PQexec ("end") ;
 
Why did the backend die?
When I do a query-all on the data I get an infinite loop; no output.
Does anybody know why this is happening?
 
New info: this loop always dies at just over 2000 tuples;
maybe always at exactly 2098.  Notice that this is within
a begin/end transaction and there may be a maximum.  Anyway
I append 2000 records at a time now and it works.

steved@cfcl.com