8.0.0beta2 and plpgsql - Mailing list pgsql-general

From Stefano Bonnin
Subject 8.0.0beta2 and plpgsql
Date
Msg-id 031f01c49bfe$8eef9180$0501a8c0@comai04
Whole thread Raw
List pgsql-general
Hi,
 
I have a problem with plpgsql and postgres8.0.0beta2
 
When I execute an insert on "mytable" the psql client returns me the following:
 
****
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed
***
 
on the server side (logfile)
 
2004-09-16 16:57:51 CEST  postgres crs LOG:  statement: INSERT INTO "SNS_DATA"
("Cod_Par","Cod_Ana","Valore","Descriz","Un_Mis","Cod_Luogo", "Data_Arrivo_Campione",site_id,hash) VALUES ('24359','2004-09-11 03:00:0057',19.8,'Temperatura media []','°C','57',timestamp '2004-09-11 03:00:00',1,-574156802);

2004-09-16 16:57:51 CEST   LOG:  server process (PID 794) was terminated by signal 11
2004-09-16 16:57:51 CEST   LOG:  terminating any other active server processes
2004-09-16 16:57:51 CEST   LOG:  all server processes terminated; reinitializing
2004-09-16 16:57:51 CEST   LOG:  database system was interrupted at 2004-09-16 16:57:46 CEST
2004-09-16 16:57:51 CEST   LOG:  checkpoint record is at 0/895B80C4
2004-09-16 16:57:51 CEST   LOG:  redo record is at 0/895B80C4; undo record is at 0/0; shutdown TRUE
2004-09-16 16:57:51 CEST   LOG:  next transaction ID: 12802; next OID: 11837631
2004-09-16 16:57:51 CEST   LOG:  database system was not properly shut down; automatic recovery in progress
2004-09-16 16:57:51 CEST   LOG:  record with zero length at 0/895B8100
2004-09-16 16:57:51 CEST   LOG:  redo is not required
2004-09-16 16:57:52 CEST   LOG:  database system is ready
 
that is a segfault error.
The error is generated by a plpgsql function that it was correct on the 7.4.2 engine.
Are there any changes in the plpgsql environment of the 8.0.0beta version?
The *terrible* problem is that postgres doesn't give me any line reference of the error.
Obviously, if I drop the plpgsql function the isert goes right.
 
Could be a bug?
Thanks in advance.
 
Reds.
 
PS. If this is not the right place where to post this problem please give me a more appropriated list.
 

pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Not even JPEGs are safe?
Next
From: Shelby Cain
Date:
Subject: Re: Not even JPEGs are safe?