Hi,
I have the following problem: the backend crashes on Solaris while executing the function
SPI_getvalue.
I have small database on Intel/Linux that works fine. Now I need to transfer them to
Sparc/Solaris. This database contains a small trigger written in C++. After installing
postgresql-7.0.3 on Solaris and compiling the trigger function by inserting a new row in table I
receive the following:
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
connection to server was lost
And in postgres log I receive:
DEBUG: start update_prednet_words function
DEBUG: before 1 SPI
DEBUG: triggered for relation magazine
Server process (pid 1397) exited with status 139 at Sun Jan 28 17:23:48 2001
Terminating any active server processes...
Server processes were terminated at Sun Jan 28 17:23:48 2001
Reinitializing shared memory and semaphores
DEBUG: Data Base System is starting up at Sun Jan 28 17:23:48 2001
DEBUG: Data Base System was interrupted being in production at Sun Jan 28 17:23:30 2001
DEBUG: Data Base System is in production state at Sun Jan 28 17:23:48 2001
First 3 lines are from my C-function, after logging the string "triggered for relation ..." it calls
SPI_getvalue. And the backend crashes. And this happens on Solaris 2.6 and Solaris 2.8 for both
postgresql-7.0.2 and 7.0.3. At the same time on Linux this trigger works fine.
Is this a bug or my misconfuguration?
My setup is
Linux: RedHat 6.2, Intel Pentium II-400, 128 Mb
Solris: SunOS 5.8 Generic_108528-02 sun4u sparc SUNW,Ultra-60,
SunOS 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-1
postgres is configured in the following way:
./configure --enable-locale --enable-multibyte=UNICODE
Best regards,
Alex Guryanow