Thread: crash in 9.1's psql:describeOneTableDetails
Hi,
Timing is on.
Pager is always used.
psql (9.1devel, server 9.0.3)
WARNING: psql version 9.1, server version 9.0.
Some psql features might not work.
Type "help" for help.
# \d category
column number 2 is out of range 0..1
results in:
Program received signal SIGSEGV, Segmentation fault.
__strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:106
106 ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory.
in ../sysdeps/x86_64/multiarch/../strcmp.S
(gdb) bt
#0 __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:106
#1 0x000000000041ec48 in describeOneTableDetails (schemaname=0x1f8ca06
"easyshop",
relationname=0x1f8ca0f "category", oid=0x1f8ca00 "48441", verbose=0
'\000') at describe.c:1757
#2 0x000000000041cfac in describeTableDetails (pattern=0x1f8c570 "category",
verbose=0 '\000', showSystem=0 '\000')
at describe.c:1069
#3 0x0000000000404407 in exec_command (cmd=0x1f82e70 "d",
scan_state=0x1f70050, query_buf=0x1f70690)
at command.c:369
#4 0x0000000000403be2 in HandleSlashCmds (scan_state=0x1f70050,
query_buf=0x1f70690) at command.c:108
#5 0x000000000040d7ce in MainLoop (source=0x7f40888fc7e0) at mainloop.c:301
#6 0x0000000000413085 in main (argc=8, argv=0x7fff05473d08) at startup.c:305
Unfortunately I wont have time to
Hi, Sorry, I unfortunately had the wrong window focused when hitting enter... On Thursday, February 10, 2011 10:47:42 AM Andres Freund wrote: > Timing is on. > Pager is always used. > psql (9.1devel, server 9.0.3) > WARNING: psql version 9.1, server version 9.0. > Some psql features might not work. > Type "help" for help. > > > # \d category > column number 2 is out of range 0..1 > > results in: > > Program received signal SIGSEGV, Segmentation fault. > __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:106 > 106 ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory. > in ../sysdeps/x86_64/multiarch/../strcmp.S > (gdb) bt > #0 __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:106 > #1 0x000000000041ec48 in describeOneTableDetails (schemaname=0x1f8ca06 > "easyshop", > relationname=0x1f8ca0f "category", oid=0x1f8ca00 "48441", verbose=0 > '\000') at describe.c:1757 > #2 0x000000000041cfac in describeTableDetails (pattern=0x1f8c570 > "category", verbose=0 '\000', showSystem=0 '\000') > at describe.c:1069 > #3 0x0000000000404407 in exec_command (cmd=0x1f82e70 "d", > scan_state=0x1f70050, query_buf=0x1f70690) > at command.c:369 > #4 0x0000000000403be2 in HandleSlashCmds (scan_state=0x1f70050, > query_buf=0x1f70690) at command.c:108 > #5 0x000000000040d7ce in MainLoop (source=0x7f40888fc7e0) at > mainloop.c:301 #6 0x0000000000413085 in main (argc=8, > argv=0x7fff05473d08) at startup.c:305 > > Unfortunately I wont have time to to analyze this properly today, so if somebody is motivated before that... Thats psql from REL9_1_ALPHA3-321-g036bb15 Greetings, Andres
On Thursday, February 10, 2011 10:50:38 AM Andres Freund wrote: > Hi, > > Sorry, I unfortunately had the wrong window focused when hitting enter... > > # \d category > > column number 2 is out of range 0..1 > > > > results in: > > > > Program received signal SIGSEGV, Segmentation fault. Ok, found the bug, simple oversight in invalid foreign key patch. Andres
On Sat, 2011-02-12 at 15:39 +0100, Andres Freund wrote: > On Thursday, February 10, 2011 10:50:38 AM Andres Freund wrote: > > Hi, > > > > Sorry, I unfortunately had the wrong window focused when hitting enter... > > > # \d category > > > column number 2 is out of range 0..1 > > > > > > results in: > > > > > > Program received signal SIGSEGV, Segmentation fault. > Ok, found the bug, simple oversight in invalid foreign key patch. > > Andres Thanks, will apply. -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services