Re: [HACKERS] Problem to current-status information in shared memory patch

2006-06-22 Thread Tom Lane
Qingqing Zhou [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] wrote postgres --single works for me. Maybe you need a make distclean/rebuild? Sorry, because I forget to say that you need to turn stats_command_string on. Ah. OK, fixed. regards, tom lane

[HACKERS] Problem to current-status information in shared memory patch

2006-06-21 Thread Qingqing Zhou
On CVS tip: $ postgres --single -Ddata postgres PostgreSQL stand-alone backend 8.2devel Segmentation fault (core dumped) $ gdb -c core.18119 (gdb) bt #0 pgstat_report_activity (cmd_str=0x67d25e IDLE) at pgstat.c:1484 1484beentry-st_changecount++; (gdb) bt #0 pgstat_report_activity

Re: [HACKERS] Problem to current-status information in shared memory patch

2006-06-21 Thread Tom Lane
Qingqing Zhou [EMAIL PROTECTED] writes: Ooops, guess we forget to handle the single user mode in current-status information in shared memory patch ... postgres --single works for me. Maybe you need a make distclean/rebuild? regards, tom lane

Re: [HACKERS] Problem to current-status information in shared memory patch

2006-06-21 Thread Qingqing Zhou
Tom Lane [EMAIL PROTECTED] wrote postgres --single works for me. Maybe you need a make distclean/rebuild? Sorry, because I forget to say that you need to turn stats_command_string on. When it is off, pgstat_report_activity() will return immediately so nothing wrong could be observed.