Re: table schema causes crash

>
>> Let me ask --- if you execute \a, then \d in psql, does it display OK?
>> How about \x and then \d?
>
> I created the table as described earlier, it segmentation fault. I ran
> psql again, then:
>
> authtest=# \d imap_passwd
> Table "imap_passwd"
> Column | Type | Modifiers
> ----------+------------------------+-----------
> username | character varying(128) | Primary key: imap_passwd_pkey
>
> *** NOTE: it only shows the first column and none of the other columns
> ***
[...]

After doing more \d on various tables, it finally core dumped on the psql
binary with debug symbols:

This GDB was configured as "alpha-unknown-netbsd"...
Core was generated by `psql'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/libexec/ld.elf_so...done.
Loaded symbols for /usr/libexec/ld.elf_so
Reading symbols from /usr/local/lib/libpq.so.2...done.
Loaded symbols for /usr/local/lib/libpq.so.2
Reading symbols from /usr/lib/libz.so.0...done.
Loaded symbols for /usr/lib/libz.so.0
Reading symbols from /usr/lib/libcrypt.so.0...done.
Loaded symbols for /usr/lib/libcrypt.so.0
Reading symbols from /usr/lib/libresolv.so.1...done.
Loaded symbols for /usr/lib/libresolv.so.1
Reading symbols from /usr/lib/libm.so.0...done.
Loaded symbols for /usr/lib/libm.so.0
Reading symbols from /usr/lib/libutil.so.6...done.
Loaded symbols for /usr/lib/libutil.so.6
Reading symbols from /usr/lib/libedit.so.2...done.
Loaded symbols for /usr/lib/libedit.so.2
Reading symbols from /usr/lib/libcurses.so.5...done.
Loaded symbols for /usr/lib/libcurses.so.5
Reading symbols from /usr/lib/libc.so.12...done.
Loaded symbols for /usr/lib/libc.so.12
#0 0x160275d84 in strlen () from /usr/lib/libc.so.12
(gdb) bt
#0 0x160275d84 in strlen () from /usr/lib/libc.so.12
#1 0x120010a10 in print_aligned_text (title=0x120015a94 "\002", headers=0xc,
cells=0x12003a550, footers=0x0, opt_align=0x120020cc4 "Primary key",
opt_barebones=1 '\001', opt_border=0, fout=0x12003a540) at print.c:280