Re: [QUESTIONS] Re: [HACKERS] text should be a blob field - Mailing list pgsql-hackers

From Peter T Mount
Subject Re: [QUESTIONS] Re: [HACKERS] text should be a blob field
Date
Msg-id Pine.LNX.3.95.980306065114.8393A-100000@maidast
Whole thread Raw
In response to Re: [QUESTIONS] Re: [HACKERS] text should be a blob field  ("Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>)
List pgsql-hackers
On Thu, 5 Mar 1998, Vadim B. Mikheev wrote:

> Peter T Mount wrote:
> >
> > On Tue, 3 Mar 1998, Bruce Momjian wrote:
> >
> > > > make text a blob datatype (maybe storing <= 8k row with tuple, >=8k in blob
> > > > tablespace)
> > >
> >
> > There was some talk about this about a month ago.
> >
> > Although we now have blob support in the JDBC driver, there is one
> > outstanding issue with them, that I was waiting for 6.3 to be released
> > before starting on it (and almost certainly starting a discussion here
> > about it).
> >
> > Allowing text to use blobs for values larger than the current block size
> > would hit the same problem.
>
> When I told about multi-representation feature I ment that applications
> will not be affected by how text field is stored - in tuple or somewhere
> else. Is this Ok for you ?

Yes. What I was meaning was if the "somewhere else" is in a blob, then we
would have to keep track of it if the tuple is updated or deleted.

--
Peter T Mount  petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk


pgsql-hackers by date:

Previous
From: Peter T Mount
Date:
Subject: Re: [HACKERS] Speedups
Next
From: Goran Thyni
Date:
Subject: Re: [HACKERS] AUTO_INCREMENT suggestion