BUG #3796: crash after select from indexed columns

From: "Matthias" <matthias(dot)schoeneich(at)gmx(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3796: crash after select from indexed columns
Date: 2007-12-03 21:29:10
Message-ID: 200712032129.lB3LTAH1000399@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 3796
Logged by: Matthias
Email address: matthias(dot)schoeneich(at)gmx(dot)net
PostgreSQL version: 8.3beta3
Operating system: Win XP SP2
Description: crash after select from indexed columns
Details:

Hi all,

I'm not sure if this is the correct group to post, so please feel free to
move this report to the correct one.
Playing with the beta I was able to crash the server(fresh installed, no
config change except logging) with a simple select. Maybe you are able to
reproduce the behavior using the following script. I added as much
information as I could get (script output, server log and windows event
log).

Best regards
Matthias
(sorry for my bad english)

------------------------------------
script------------------------------------
select version();
drop table if exists test;
create table test (test_id integer ,
value integer );

create index test_value_id on test(value,test_id);

select max(test_id) from test where value is null;

------------------------------------ script output
------------------------------------
version
--------------------------------------------------------
PostgreSQL 8.3beta3, compiled by Visual C++ build 1400
(1 row)

psql:C:/Temp/Edit781:3: NOTICE: table "test" does not exist, skipping
DROP TABLE
CREATE TABLE
CREATE INDEX
psql:C:/Temp/Edit781:10: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
psql:C:/Temp/Edit781:10: connection to server was lost

------------------------------------ server log
------------------------------------
2007-12-03 21:42:53 CET LOG: 00000: statement: select max(test_id) from
test where value is null;
2007-12-03 21:42:53 CET LOCATION: exec_simple_query,
.\src\backend\tcop\postgres.c:827

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.

2007-12-03 21:42:55 CET LOG: 00000: server process (PID 2572) exited with
exit code 3
2007-12-03 21:42:55 CET LOCATION: LogChildExit,
.\src\backend\postmaster\postmaster.c:2490
2007-12-03 21:42:55 CET LOG: 00000: terminating any other active server
processes
2007-12-03 21:42:55 CET LOCATION: HandleChildCrash,
.\src\backend\postmaster\postmaster.c:2355
2007-12-03 21:42:55 CET LOG: 00000: all server processes terminated;
reinitializing
2007-12-03 21:42:55 CET LOCATION: PostmasterStateMachine,
.\src\backend\postmaster\postmaster.c:2663
2007-12-03 21:42:56 CET FATAL: XX000: pre-existing shared memory block is
still in use
2007-12-03 21:42:56 CET HINT: Check if there are any old server processes
still running, and terminate them.
2007-12-03 21:42:56 CET LOCATION: PGSharedMemoryCreate,
.\src\backend\port\win32_shmem.c:168

------------------------------------ windows event log
------------------------------------
TRAP: FailedAssertion("!(((rinfo->clause) != ((void *)0) &&
((((Node*)(rinfo->clause))->type) == T_OpExpr)))", File:
".\src\backend\optimizer\plan\planagg.c", Line: 371)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-12-03 22:38:03 Re: BUG #3796: crash after select from indexed columns
Previous Message Magnus Hagander 2007-12-03 15:12:13 Re: BUG #3790: pg_restore error canceling statement due to user request