Re: BUG #3301: explain crashes server on simple (?) query

From: Leszek Trenkner <olaf(at)post(dot)pl>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3301: explain crashes server on simple (?) query
Date: 2007-05-24 17:06:02
Message-ID: 39de3$4655c5fb$594f4043$2650@news.chello.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:

> "Leszek Trenkner" <olaf(at)post(dot)pl> writes:
>> I'll post schema for bug recreation on pgsql-bugs.
>
> Yes?
>
> regards, tom lane

Well, I bug appeared on list with a long delay, so in the morning I didn't
notice it yet. Database dump that allows me to recreate situation comes
attached. It's a really simple query, and today I reproduced the very same
crash on different machine.

It doesn't happen on stock Ubuntu's 8.2 ("PostgreSQL 8.2.4 on
i486-pc-linux-gnu, compiled by GCC cc (GCC) 4.1.2 (Ubuntu
4.1.2-0ubuntu4)").

Server log with 'debug5' level:

"PostgreSQL 8.3devel on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.2
(Ubuntu 4.1.2-0ubuntu4)"
--------------------------------------------------------------------------
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: DEBUG: 00000:
StartTransactionCommand
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: LOCATION:
start_xact_command, postgres.c:2248
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: STATEMENT:
explain select t.id, foo.name from t join
(select ta.id, ta.name from ta
union select tb.id, tb.name from tb
) foo on foo.id = any (t.ids);

2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: DEBUG: 00000:
StartTransaction
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: LOCATION:
ShowTransactionState, xact.c:4031
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: STATEMENT:
explain select t.id, foo.name from t join
(select ta.id, ta.name from ta
union select tb.id, tb.name from tb
) foo on foo.id = any (t.ids);

2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: DEBUG: 00000:
name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid:
757/1/0, nestlvl: 1, children: <>
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: LOCATION:
ShowTransactionStateRec, xact.c:4056
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: STATEMENT:
explain select t.id, foo.name from t join
(select ta.id, ta.name from ta
union select tb.id, tb.name from tb
) foo on foo.id = any (t.ids);

2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> EXPLAIN: DEBUG: 00000:
ProcessUtility
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> EXPLAIN: LOCATION:
PortalRunUtility, pquery.c:1142
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> EXPLAIN: STATEMENT:
explain select t.id, foo.name from t join
(select ta.id, ta.name from ta
union select tb.id, tb.name from tb
) foo on foo.id = any (t.ids);

2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: reaping dead processes
2007-05-24 18:55:50 CEST <@ > : LOCATION: reaper, postmaster.c:2022
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: server process (PID 9253) was
terminated by signal 11: Segmentation fault
2007-05-24 18:55:50 CEST <@ > : LOCATION: LogChildExit, postmaster.c:2460
2007-05-24 18:55:50 CEST <@ > : LOG: 00000: server process (PID 9253) was
terminated by signal 11: Segmentation fault
2007-05-24 18:55:50 CEST <@ > : LOCATION: LogChildExit, postmaster.c:2460
2007-05-24 18:55:50 CEST <@ > : LOG: 00000: terminating any other active
server processes
2007-05-24 18:55:50 CEST <@ > : LOCATION: HandleChildCrash,
postmaster.c:2332
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: sending SIGQUIT to process
9248
2007-05-24 18:55:50 CEST <@ > : LOCATION: HandleChildCrash,
postmaster.c:2369
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: sending SIGQUIT to process
9247
2007-05-24 18:55:50 CEST <@ > : LOCATION: HandleChildCrash,
postmaster.c:2369
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: sending SIGQUIT to process
9240
2007-05-24 18:55:50 CEST <@ > : LOCATION: HandleChildCrash,
postmaster.c:2383
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: sending SIGQUIT to process
9242
2007-05-24 18:55:50 CEST <@ > : LOCATION: HandleChildCrash,
postmaster.c:2395
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: sending SIGQUIT to process
9241
2007-05-24 18:55:50 CEST <@ > : LOCATION: HandleChildCrash,
postmaster.c:2417
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: reaping dead processes
2007-05-24 18:55:50 CEST <@ > : LOCATION: reaper, postmaster.c:2022
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: WARNING: 57P02:
terminating connection because of crash of another server process
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server process exited abnormally and
possibly corrupted shared memory.
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: HINT: In a moment
you should be able to reconnect to the database and repeat your command.
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 crash> idle: LOCATION:
quickdie, postgres.c:2405
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 postgres> idle: WARNING:
57P02: terminating connection because of crash of another server process
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 postgres> idle: DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server process exited abnormally and
possibly corrupted shared memory.
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 postgres> idle: HINT: In a
moment you should be able to reconnect to the database and repeat your
command.
2007-05-24 18:55:50 CEST <postgres(at)127(dot)0(dot)0(dot)1 postgres> idle: LOCATION:
quickdie, postgres.c:2405
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: reaping dead processes
2007-05-24 18:55:50 CEST <@ > : LOCATION: reaper, postmaster.c:2022
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: server process (PID 9247)
exited with exit code 2
2007-05-24 18:55:50 CEST <@ > : LOCATION: LogChildExit, postmaster.c:2440
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: server process (PID 9248)
exited with exit code 2
2007-05-24 18:55:50 CEST <@ > : LOCATION: LogChildExit, postmaster.c:2440
2007-05-24 18:55:50 CEST <@ > : LOG: 00000: all server processes
terminated; reinitializing
2007-05-24 18:55:50 CEST <@ > : LOCATION: reaper, postmaster.c:2228
2007-05-24 18:55:50 CEST <@ > : DEBUG: 00000: shmem_exit(0)
2007-05-24 18:55:50 CEST <@ > : LOCATION: shmem_exit, ipc.c:155
----------------------------------------------------------------------------------------
Well, previous crash report was in fact from Debian 4.0 host, not Ubuntu:
"PostgreSQL 8.3devel on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.2
20061115 (prerelease) (Debian 4.1.1-21)"
--
Greetings. Leszek Trenkner

Attachment Content-Type Size
crash_clean.sql text/plain 2.7 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-05-24 18:59:43 Re: BUG #3301: explain crashes server on simple (?) query
Previous Message Teodor Sigaev 2007-05-24 15:45:02 Re: BUG #3302: Crash on gist ltree - PANIC: failed to add item to index page