From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tom(at)minnesota(dot)com |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-general(at)postgresql(dot)org |
Subject: | Re: table schema causes crash |
Date: | 2003-01-07 22:03:36 |
Message-ID: | 200301072203.h07M3aB19036@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Was a cause ever found for this?
---------------------------------------------------------------------------
tom(at)minnesota(dot)com wrote:
> > <tom(at)minnesota(dot)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
> [...]
>
> \d on any table shows only the first column:
>
> authtest=# \d country
> Table "country"
> Column | Type | Modifiers
> ------------+---------+-----------
> country_id | integer | Primary key: country_pkey
>
> authtest=# \d auth_address
> Table "auth_address"
> Column | Type | Modifiers
> ------------+---------+-----------
> address_id | integer | Primary key: auth_address_pkey
> Unique keys: auth_address_user_id_key
> Triggers: RI_ConstraintTrigger_9306303,
> RI_ConstraintTrigger_9306352,
> RI_ConstraintTrigger_9306354
>
> authtest=# \d auth_email
> Table "auth_email"
> Column | Type | Modifiers
> ----------+---------+-----------
> email_id | integer | Primary key: auth_email_pkey
> Unique keys: auth_email_em_idx,
> auth_email_ev_idx,
> auth_email_user_id_key
> Triggers: RI_ConstraintTrigger_9324514
>
> ---
>
> All of the above table came from the same db. However, when I connect to a
> different database, things are normal again:
>
> authtest=# \c transition
> You are now connected to database transition.
> transition=# \d t_blocks
> Table "t_blocks"
> Column | Type | Modifiers
> --------------+--------------------------+-----------
> rid | character varying(16) | atthasdef
> display | character(1) | ?
> heading | character varying(48) |
> content | text | ter(1)
> url | character varying(96) |
> type | smallint |
> birthstamp | timestamp with time zone | pgsql
> timestamp | timestamp with time zone | l
> showmain | character(1) | ?
> hits | integer |
> cache | integer |
> pagecomments | character(1) |
> orderid | smallint | zone
> Primary key: t_blocks_pkey
>
> ---
> But note the Modifiers column. There are some very odd values in there.
>
> Could it be related to the fact that in 7.2 and earlier, didn't use the flag:
>
> --enable-multibyte
>
> I only started using --enable-multibyte in 7.2.3.
>
>
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-01-07 22:17:17 | Re: Ora2pg new update |
Previous Message | Achilleus Mantzios | 2003-01-07 21:55:33 | 7.3.1 function problem: ERROR: cache lookup failed for type 0 |