Skip site navigation (1) Skip section navigation (2)

Re: C set return function differences on 8.0?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Tim Jackson <tim(dot)jackson(at)ints(dot)com>,pgsql-interfaces(at)postgresql(dot)org
Subject: Re: C set return function differences on 8.0?
Date: 2005-07-09 02:13:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> On Fri, Jul 08, 2005 at 05:12:58PM -0700, Tim Jackson wrote:
>> The backend crashes, in pgadmin  attempting to display the view simple 
>> says aborting.  There is no core dump, and the log only seems to reflect 
>> the standard
>> WARNING:  terminating connection because of crash of another server process

> Where did you look for a core dump?

"There is no core dump" is not an acceptable answer: if there isn't one,
the first item on your agenda must be to get one (or else run the
problem case under gdb so you don't need a dump to get a stack trace).

Usually if there's no dump it's because the default configuration on
your system is "ulimit -c 0" to suppress core dumps from daemons.
Put "ulimit -c unlimited" (or local equivalent) into your postmaster
start script and restart the postmaster.

On the whole though I'd recommend learning how to attach gdb to a live
backend, since then not only can you get a stack trace from the point of
the fault, but you can then work backwards by setting breakpoints ahead
of the crash and stepping through the code to see where it goes wrong.

			regards, tom lane

In response to

pgsql-interfaces by date

Next:From: Dirk JagdmannDate: 2005-07-09 21:26:00
Subject: ecpg and VARCHAR
Previous:From: Michael FuhrDate: 2005-07-09 01:58:00
Subject: Re: C set return function differences on 8.0?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group