Problem to "current-status information in shared memory" patch

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Problem to "current-status information in shared memory" patch
Date: 2006-06-22 03:31:56
Message-ID: e7d2vv$o75$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-06-22 03:48:12 Re: Problem to "current-status information in shared memory" patch
Previous Message Qingqing Zhou 2006-06-22 03:01:14 Re: Out of memory error in 8.1.0 Win32