Problem to "current-status information in shared memory" patch - Mailing list pgsql-hackers

From Qingqing Zhou
Subject Problem to "current-status information in shared memory" patch
Date
Msg-id e7d2vv$o75$1@news.hub.org
Whole thread Raw
Responses Re: Problem to "current-status information in shared memory" patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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
1484            beentry->st_changecount++;
(gdb) bt
#0  pgstat_report_activity (cmd_str=0x67d25e "<IDLE>") at pgstat.c:1484
#1  0x000000000056db8c in PostgresMain (argc=1, argv=0x8657d8,   username=0x867030 "qqzhou") at postgres.c:3132
#2  0x000000000050c918 in main (argc=4, argv=0x8657d0) at main.c:372
(gdb) p beentry
$1 = (volatile PgBackendStatus *) 0x0

Ooops, guess we forget to handle the single user mode in "current-status
information in shared memory" patch ...

Regards,
Qingqing




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Overhead for stats_command_string et al, take 2
Next
From: Tom Lane
Date:
Subject: Re: Problem to "current-status information in shared memory" patch