Re: Need some help: attlen is pg_attributes gives a negative value.. .

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: roberts(at)panix(dot)com, pgsql-sql(at)postgresql(dot)org, bugs(at)postgresql(dot)org
Subject: Re: Need some help: attlen is pg_attributes gives a negative value.. .
Date: 2000-05-05 04:12:40
Message-ID: 200005050412.AAA09310@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Roland Roberts <roberts(at)panix(dot)com> writes:
> >>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Tom> Must have been quite a few versions back; attlen has been -1
> Tom> for variable-length datatypes for as long as I've been paying
> Tom> attention. (Of course char(n) isn't *really* variable length,
> Tom> but it's treated that way so that the representation is the
> Tom> same as for varchar(n) and text.)
>
> > When did this change? I haven't looked 6.5, but I thought 6.3 still
> > has bpchar as fixed length and char(n) was blank padded whereas
> > varchar was not.
>
> char(n) was and is blank-padded, varchar(n) was and is not. Sorry
> if I was imprecise enough to convey a different impression.
>
> I'm fairly sure that attlen had its present semantics in 6.4. 6.3
> was before my time; any old-timers care to comment?

Since day 1, they were that way. atttypmod was added in 6.3.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Roland Roberts 2000-05-05 04:39:18 Re: Need some help: attlen is pg_attributes gives a negative value.. .
Previous Message Tom Lane 2000-05-05 03:25:11 Re: query slowness caused by table alias