Content-Type: text/plain;
  charset="iso-8859-1"
From: sad <sad@bankir.ru>
Organization: IT
To: "psql" <pgsql-sql@postgresql.org>
Subject: Re: Large Objects and Bytea
Date: Thu, 25 Sep 2003 08:55:57 +0400
User-Agent: KMail/1.4.3
References: <00f701c3831b$242f2150$7502a8c0@hdsc.com>
In-Reply-To: <00f701c3831b$242f2150$7502a8c0@hdsc.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200309250855.57219.sad@bankir.ru>

Hi, Friends !

On Thursday 25 September 2003 08:11, you wrote:

> I am migrating MS SQL DB to Postgres DB. I have tables with columns of da=
ta
> type 'Image' in the MS SQL database. IF I choose 'bytea' datatype, I am
> afraid it may lead to poor performance of the database (which I read from
> the manual). In this case what is the best data type to use.

I am using TEXT fields to store images and pdfs.
There is one "feature": ZERO bytes causes interruption of input and output.
so I am translating Zeroes to '#0' and '#' to '#1' (it is similar to work w=
ith=20
bytea)
I am really not sure that's the best, but usefull.

BTW, i ask Developers: can you remove this "feature" of ZEROES in a TEXT ?
AFAIK the TEXT-type itself allows ANY bytes to store !=20
(its length representet explisitly in 4 bytes)
The "feature" obviosly grown from C strings......