Re: table schema causes crash

scott.marlowe <scott.marlowe@ihs.com>

From: "scott.marlowe" <scott.marlowe@ihs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: <tom@minnesota.com>, <pgman@candle.pha.pa.us>, <pgsql-general@postgresql.org>
Date: 2002-12-20T23:24:29Z
Lists: pgsql-general
On Fri, 20 Dec 2002, Tom Lane wrote:

> <tom@minnesota.com> writes:
> > 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 ***
> 
> What I find even more suspicious is that the "Primary key" footer shows
> up in the table data area.  Looking at print_aligned_text, this seems to
> suggest that cells[2] must be NULL --- you would get this kind of
> mistake if the number of non-null cells[] entries is not a multiple of
> the number of non-null headers[] entries.  But I surely do not see how
> describeTableDetails would be setting that cell to null --- it does
> 
> 			cells[i * cols + 2] = xmalloc(128 + 128);
> 
> and xmalloc() will exit() rather than return null.

This is sounding more and more like a machine with bad memory or a bad 
hard drive.