Hi Guys,
Here is a gdb dump of the backtrace at the server process crash. I have also included the code that generates these
calls.As mentioned below this specific connection has been used many times before the crash. Also, we are aware of the
threadcaveat that only using a connection from one thread at a time. Therefore the "strange" connection name that
includesboth the process id and the thread id. This is for the code to make sure that a connection is only used in the
threadit is meant to.
Hope this can help in helping me ;-),
Leif
----- Original Message -----
> On 05/06/2014 11:37 PM, Leif Jensen wrote:
> > Hello Adrian,
> >
> > Thank you for your answer. I can post part of the code that
> > makes these calls, but I'm not sure how much it would help. It
> > is rather large function that makes these calls, and it is
> > called all over the program. The part of the log posted is only
> > a small excerpt of the use of the
> > ApplDBConn_22854_f6adeb70_query, which has been used many many
> > times before the log shown (167 in all to be exact ;-) ).
>
> Exactly. Something different happened at that point. The hard part
> will
> determining what that is. The next step would seem to run a debugger
> on
> the Postgres process to get more information. For a step by step guide
> see here:
>
> https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
>
> >
> > Leif
> >
> >
>
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
