From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] rollback varchar change |
Date: | 1998-01-08 05:54:15 |
Message-ID: | 34B46A07.DAEA1086@sable.krasnoyarsk.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> >
> > Bruce Momjian wrote:
> > >
> > > I have found that the varchar() change I made requires a new
> > > pg_attribute field, so I am rolling back the change until I get a fully
> > ^^^^^^^^^^^^^^^^^^
> >
> > Please try some other way. As I remember, you said about breaking
> > vl_len into 2 parts - very nice for me, but I'd recommend to leave
> > varlena as is and add new structure - for compatibility and to allow
> > text (etc) be longer 2^16 someday (multi-representation feature).
> > Just like attlen -1 is used in many parts of code to flag varlena,
> > you could use -2 to flag new structure.
>
> OK, I have now figured out that my original idea was sound. The only
Having new column in pg_attribute I'm not sure that we need in new
structure...
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-01-08 06:16:25 | Re: [HACKERS] varchar() change |
Previous Message | Vadim B. Mikheev | 1998-01-08 05:51:45 | Re: [HACKERS] varchar() change |