Re: pg_dumpall failing from possible corrupted shared memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
Cc: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dumpall failing from possible corrupted shared memory
Date: 2006-10-26 13:57:17
Message-ID: 13003.1161871037@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Richard Broersma Jr <rabroersma(at)yahoo(dot)com> writes:
> I did not find any coredump files. Will I need to rebuild postgres to produce coredumps?

No, you just need to make sure the postmaster is started under
"ulimit -c unlimited", not "ulimit -c 0" which is the default
under many Linuxen. Adding this to the start script is the
easiest way usually.

If you can't get anything but numbers from gdb's stack trace
then you have a "stripped" executable and you will need to
rebuild to get a useful stack trace.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2006-10-26 14:57:03 Re: password cookie
Previous Message Linder Poclaba 2006-10-26 13:47:46 Re: identificar usuario con registro en una tabla