On 10/03/2011 10:10 AM, Robert Burgholzer wrote: > FWIW - I am currently trying this while tracing the process that I > assume is the postmaster (/usr/bin/postgres -D /home/postgres/data), > since this process number indicates that it was recently restarted - > although the other PG processes, writer, wal writer, autovacuum, stats > collector all have their older pids indicating that they still survive. Sounds like you are attaching to the wrong process. Try something like the below... Joe Session #1: (connect to db and load PL/R) ----------------- #psql contrib_regression psql (9.2devel) Type "help" for help. contrib_regression=# load '$libdir/plr'; LOAD Session #2: (use ps to find backend and attach) ----------------- # ps -ef |grep postgres postgres 17001 1 0 Sep24 ? 00:00:16 /usr/local/pgsql-head/bin/postgres -D /usr/local/pgsql-head/data -p 55437 -i postgres 17006 17001 0 Sep24 ? 00:02:18 postgres: writer process postgres 17007 17001 0 Sep24 ? 00:01:50 postgres: wal writer process postgres 17008 17001 0 Sep24 ? 00:00:37 postgres: autovacuum launcher process postgres 17009 17001 0 Sep24 ? 00:00:47 postgres: stats collector process postgres 26631 17001 0 10:22 ? 00:00:00 postgres: postgres contrib_regression [local] idle #gdb /usr/local/pgsql-head/bin/postgres 26631 (gdb) continue Continuing. Session #1: (run crashing function) ----------------- run your PL/R function that causes the crash -- Joe Conway credativ LLC: http://www.credativ.us Linux, PostgreSQL, and general Open Source Training, Service, Consulting, & 24x7 Support -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
