On Wed, 2006-07-12 at 07:32, Carl M. Nasal II wrote:
> I apologize for not including the server information in the last e-mail. I
> knew I would forget something. :)
>
> PostgreSQL 8.1.4 (compiled from source)
> Debian GNU/Linux 3.1
> Intel(R) Pentium(R) D CPU 3.00GHz
> 1GB RAM
>
> We have not
I apologize for not including the server information in the last e-mail. I
knew I would forget something. :)
PostgreSQL 8.1.4 (compiled from source)
Debian GNU/Linux 3.1
Intel(R) Pentium(R) D CPU 3.00GHz
1GB RAM
We have not be able to test the triggers anywhere else that has any load on
it.
Thanks for the tips. I will try to use the strict pragma as you suggested
and see if it helps.
The code runs fine most of the time. The issue is as time elapses, the
server ends up crashing. Generally, it will crash within a day of use
(with only 3 clients hitting it). The reason we believ
2006/7/11, Carl M. Nasal II <[EMAIL PROTECTED]>:
(...)
Any ideas of what is causing the server to crash will be helpful.
Below are the lines from the PostgreSQL serverlog file when the crash occurs:
LOG: server process
Are you certain that it is the trigger that is crashing the process? If
that is true, then there may be a bug in plperl.
To debug, you could use gdb, but try this first:
Use the strict pragma. To do this in plperl (instead of plperlu), use:
BEGIN { strict->import(); }
or set strict mod
We are writing a multi-master replication process for our Electronic
Medical Records product. We have written triggers in plPHP and then in
PL/Perl to keep an audit trail of the changes as well as flags so the data
can be replicated. We started with plPHP, but then server started
crashing, wh
