Postgres Crash Running PLPGSQL Function on 8.2.3 - Mailing list pgsql-general

From Gary Winslow
Subject Postgres Crash Running PLPGSQL Function on 8.2.3
Date
Msg-id 88CCD18270AF9F46A8225246DD9B138F43916B@atfsrv1.americantaxfunding.com
Whole thread Raw
Responses Re: Postgres Crash Running PLPGSQL Function on 8.2.3
List pgsql-general

Has anyone experienced any problems with the Postgres 8.2.x database crashing when running PLPGSQL functions?

 

When I try to run my plpgsql function it causes Postgres to restart unexpectedly.   The code was working with prior versions of Postgres, now it seems to be crashing the postmaster.   Here are my log entries...

 

2007-03-27 10:20:35 LOG:  statement:

                SELECT "2007-3".getopencharge('822512', '2007-3-31', '2007-3', 'f')

2007-03-27 10:20:35 LOG:  server process (PID 3516) exited with exit code -1073741819

2007-03-27 10:20:35 LOG:  terminating any other active server processes

2007-03-27 10:20:35 WARNING:  terminating connection because of crash of another server process

2007-03-27 10:20:35 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2007-03-27 10:20:35 HINT:  In a moment you should be able to reconnect to the database and repeat your command.

2007-03-27 10:20:35 WARNING:  terminating connection because of crash of another server process

2007-03-27 10:20:35 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2007-03-27 10:20:35 HINT:  In a moment you should be able to reconnect to the database and repeat your command.

2007-03-27 10:20:35 LOG:  all server processes terminated; reinitializing

2007-03-27 10:20:35 LOG:  database system was interrupted at 2007-03-27 10:18:52 Eastern Daylight Time

 

 

When I run the function, it runs ok the first time.   The second time right after that, the crash occurs.   This is consistent every time I run this test.  

 

This problem seems to be exactly the same symptoms as a bug I reported already #3158/#3166, but have not seen much dialogue on it.   I am not sure how to correct this problem as it was already working fine in a prior version of Postgres.

 

I am running this on a Windows 2003 Standard Server SP1.   The server is an Intel P4 XEON with 1GB RAM and Ultra 320 RAID 10 Configuration.  My PostgresSQL version is 8.2.3.

 

Can any one help with this? 

 

Gary

 

pgsql-general by date:

Previous
From: pol
Date:
Subject: to build a vocabulary
Next
From: "Kev"
Date:
Subject: Re: cutting out the middleperl