Thread

backend closed the channel unexpectedly

David Wetzel <dave@turbocat.de> — 1999-05-12T00:37:16Z

Hi,

I have found a bug that is very easy to reprouduce here:

The table is created with this code:

create table DIAGNOSE (ART varchar(1) NOT NULL, AUFENTHALTNR int NOT NULL,  
CREATION_DATE datetime, CREATION_USER varchar(30), DAUERDIAGNOSENR int NOT  
NULL, MODIFICATION_DATE datetime, MODIFICATION_USER varchar(30), NR int NOT  
NULL, OPNR int, TEXT varchar(250) NOT NULL, VERWEILDAUER int, ZEIT datetime);

CREATE UNIQUE INDEX DIAGNOSE_NR ON DIAGNOSE (NR);

Then create a file that contains 100 000 times this line and save it as  
/tmp/DBTEST.sql:

INSERT INTO  DIAGNOSE (CREATION_DATE, CREATION_USER, VERWEILDAUER, ART,  
TEXT, AUFENTHALTNR, NR, OPNR, DAUERDIAGNOSENR, MODIFICATION_USER,  
MODIFICATION_DATE, ZEIT)  VALUES  ('Fri May 07 21:10:52 1999 CEST', 'USER',  
NULL, 'X', 'Noch nicht eingegeben', 71108, 316707, NULL, 0, 'USER', 'Fri May  
07 21:10:52 1999 CEST', 'Fri May 07 21:10:52 1999 CEST');


Then do

psql -q -f /tmp/DBTEST.sql mydb

Wait.

The error messages are ok. But not the closing of the backend!

Is this bug known? Are there any patches out? I use postgresql-6.4.2 on NetBSD.

NOTE: I have only subscribed pgsql-ports@postgreSQL.org

---
   _  _
 _(_)(_)_  David Wetzel, Turbocat's Development,
(_) __ (_) Buchhorster Strasse, D-16567 Muehlenbeck/Berlin, FRG,
  _/  \_   Fax +49 33056 82835 NeXTmail dave@turbocat.de
 (______)  http://www.turbocat.de/
           DEVELOPMENT * CONSULTING * ADMINISTRATION