It's possible. There is only one additional function which returns the
process id (by invoking getpid()) of the query source. You think that
could cause the problem?
My guess is it'ds because of the triggers... There are several tables
that have triggers which call stored procedures that create records
based on the records of the table whose trigger called the procedure. Is
it possible that the server returns the results of the queries while
some stored procedures run in the background?
Attila Miklosi
>Could it be that a connection may be invoking a newly recreated
>function rewritten in C that it had previously called before it's
>recreation?
>
>Allan.
On Mon, Oct 5, 2009 at 3:06 PM, Miklosi Attila <amiklosi@freemail.hu> wrote:
>
> What does the message below mean?
>
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
>
> This message appears sometimes after i send a 'BEGIN' to the server and
> the processor load of the application goes up to 99%. This happens
> usually when the application starts and several threads start sending
> queries to save the changes since the last stop.
>
> The application its locking mechanism (we are aware of that libpq
> doesn't have interlocking) has worked fine in the past. This issue has
> became serious since we moved to the latest debian lenny distribution
> and started to use libpq5.
>
> OS : Debian linux Lenny kernel version 2.6.26-2-686
> libpq : libpq5 8.3.7-0lenny
>
> Thank you in advance
> Attila Miklosi
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
