Re: Bug #883: explain analyze causes postgres to die

I included the code in the "example code" box. I'll include it again here.
If you need more info, just let me know.

I execute the command:
EXPLAIN ANALYZE INSERT INTO stubs(id, stub_id, nodecount, platform_id,
return_count)
SELECT I.id, A.stub_id, L.nodecount, P.platform_id, count(*)
FROM logdata L, id_lookup I, all_stubs A, platform P
WHERE lower(L.email) = lower(I.email)
AND L.stub_marks = A.stub_marks
AND L.os_type = P.os_type
AND L.cpu_type = P.cpu_type
AND L.version = P.version
GROUP BY I.id, A.stub_id, L.nodecount, P.platform_id;

and get back(from psql):
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset

The log shows:
2003-01-24 07:29:35 [36633] LOG: server process (pid 36657) was terminated
by signal 11
2003-01-24 07:29:35 [36633] LOG: terminating any other active server
processes
2003-01-24 07:29:35 [36633] LOG: all server processes terminated;
reinitializing shared memory and semaphores
2003-01-24 07:29:35 [36666] LOG: connection received: host=[local]
2003-01-24 07:29:35 [36666] FATAL: The database system is starting up
2003-01-24 07:29:35 [36665] LOG: database system was interrupted at
2003-01-24 07:23:52 GMT
2003-01-24 07:29:35 [36665] LOG: checkpoint record is at 26/2020EA78
2003-01-24 07:29:35 [36665] LOG: redo record is at 26/2020EA78; undo
record is at 0/0; shutdown TRUE
2003-01-24 07:29:35 [36665] LOG: next transaction id: 5758; next oid:
78509015
2003-01-24 07:29:35 [36665] LOG: database system was not properly shut
down; automatic recovery in progress
2003-01-24 07:29:35 [36665] LOG: ReadRecord: record with zero length at
26/2020EAB8
2003-01-24 07:29:35 [36665] LOG: redo is not required
2003-01-24 07:29:38 [36665] LOG: database system is ready

some info about the table:
Table "public.logdata"
Column | Type | Modifiers
------------+-----------------------+-----------
email | character varying(64) |
stub_marks | character varying(22) |
nodecount | bigint |
os_type | integer |
cpu_type | integer |
version | integer |
Indexes: logdata_cpu_version btree (cpu_type, "version"),
logdata_platform btree (os_type, cpu_type, "version")

Table "public.id_lookup"
Column | Type | Modifiers
----------+-----------------------+-----------
email | character varying(64) |
id | integer |
stats_id | integer |
Indexes: idlookup_email_lower unique btree (lower(email)),
idlookup_id btree (id)

Table "public.all_stubs"
Column | Type | Modifiers
------------+-----------------------+---------------------------------------
--------------------
stub_marks | character varying(22) | not null
stub_id | integer | not null default
nextval('"all_stubs_stub_id_seq"'::text)
project_id | smallint | not null
Indexes: all_stubs_pkey primary key btree (stub_id),
all_marks unique btree (stub_marks),
all_stubproject_id unique btree (stub_id, project_id)

Table "public.platform"
Column | Type | Modifiers
-------------+---------+----------------------------------------------------
---------------
platform_id | integer | not null default
nextval('public.platform_platform_id_seq'::text)
os_type | integer | not null
cpu_type | integer | not null
version | integer | not null
Indexes: platform_pkey primary key btree (platform_id),
platform_all btree (os_type, cpu_type, "version")

Table "public.stubs"
Column | Type | Modifiers
--------------+---------+-----------
id | integer |
stub_id | integer |
nodecount | bigint |
platform_id | integer |
return_count | integer |

logdata:
count
----------
21230697
(1 row)

id_lookup:
count
--------
393614
(1 row)

all_stubs:
count
----------
26243933
(1 row)

platform:
count
-------
140
(1 row)

stubs:
count
-------
0
(1 row)

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: <nerf(at)distributed(dot)net>; <pgsql-bugs(at)postgresql(dot)org>
Sent: Friday, January 24, 2003 12:28 AM
Subject: Re: [BUGS] Bug #883: explain analyze causes postgres to die

> pgsql-bugs(at)postgresql(dot)org writes:
> > explain analyze causes postgres to die
>
> Can't do much with this, since you have not provided a complete test
> case.
>
> regards, tom lane
>
>