From: | Joachim Wieland <joe(at)mcknight(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | postmaster segfaults with HUGE table |
Date: | 2004-11-14 09:33:01 |
Message-ID: | 20041114093301.GA23080@mcknight.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
this query makes postmaster (beta4) die with signal 11:
(echo "CREATE TABLE footest(";
for i in `seq 0 66000`; do
echo "col$i int NOT NULL,";
done;
echo "PRIMARY KEY(col0));") | psql test
ERROR: tables can have at most 1600 columns
LOG: server process (PID 2140) was terminated by signal 11
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing
Program received signal SIGSEGV, Segmentation fault.
0x4015d43c in mallopt () from /lib/tls/libc.so.6
(gdb) bt
#0 0x4015d43c in mallopt () from /lib/tls/libc.so.6
#1 0x00021680 in ?? ()
[...]
#16 0x00000001 in ?? ()
#17 0x0821bc9b in AllocSetDelete ()
Previous frame inner to this frame (corrupt stack?)
Furthermore the backend doesn't react on query cancel requests from psql
during execution of the query.
Joachim
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2004-11-14 10:05:02 | Re: postmaster segfaults with HUGE table |
Previous Message | Neil Conway | 2004-11-14 09:21:43 | GiST: PickSplit and multi-attr indexes |