From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | hackers(at)postgresql(dot)org |
Subject: | Re: varchar() troubles |
Date: | 1998-01-12 15:41:07 |
Message-ID: | 34BA3992.2B561614@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> >
> > I've been seeing trouble with varchar() columns for a little while, and
> > since it is still there with a fresh install of the development tree
> > it's time to report it:
> >
> > postgres=> create table t (v varchar(80),i int);
> > CREATE
> > postgres=> insert into t values ('hi',1);
> > INSERT 18122 1
> > postgres=> select * from t;
> > v |i
> > --+-
> > hi|0
> > (1 row)
>
> Did you see this before or only after the varchar() length change I
> made?
Pretty sure only after but it's hard to tell for sure. My trees for 971204
and 971222 both core dump on inserts to varchar, but I can't remember what
else I was doing with the trees at the time. v6.2.1p5 works OK on this:
postgres=> create table t (v varchar(80),i int);
CREATE
postgres=> insert into t values ('hi',1);
INSERT 142735 1
postgres=> select * from t;
v |i
--+-
hi|1
(1 row)
-
Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-01-12 16:35:55 | Re: [BUGS] General Bug Report: palloc fails with lots of ANDs and ORs |
Previous Message | Thomas G. Lockhart | 1998-01-12 15:27:46 | Re: [HACKERS] PSQL man page patch |