Re: Problem with PITR Past Particular WAL File

Tom:
Thanks for your help on this. The trace details are as follows:

Core was generated by `/usr/local/pgsql/bin/postgres -D /pgdata01/data'.
Program terminated with signal 11, Segmentation fault.

#0 0x080b8ee0 in entrySplitPage ()
#1 0x080baccf in ginInsertValue ()
#2 0x080b81b7 in gin_xlog_cleanup ()
#3 0x080af4ce in StartupXLOG ()
#4 0x080c04ca in BootstrapMain ()
#5 0x08186b2f in StartChildProcess ()
#6 0x081889eb in PostmasterMain ()
#7 0x0814ee9e in main ()

Cheers,
-craig

---
Craig A. McElroy
Contegix
Beyond Managed Hosting(r) for Your Enterprise

On Oct 24, 2007, at 1:26 PM, Tom Lane wrote:

> Craig McElroy <craig(dot)mcelroy(at)contegix(dot)com> writes:
>>> Can you get a stack trace from the core dump reported here?
>
>> Certainly, how can that be obtained?
>
> $ gdb /path/to/postgres-executable /path/to/core-file
> gdb> bt
> gdb> quit
>
> If you don't find a corefile in $PGDATA (or wherever your system puts
> core files) then you probably need to restart the postmaster with
> "ulimit -c unlimited" to allow producing a core.
>
> If the "bt" output is just numbers and no symbols then it won't be of
> any use; in that case you'll need to find or build non-stripped
> Postgres
> executables.
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that
> your
> message can get through to the mailing list cleanly