Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2DIQ8x72653 for ; Tue, 13 Mar 2001 13:26:08 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2DIPut20508; Tue, 13 Mar 2001 13:25:56 -0500 (EST) To: "Gordan Bobic" cc: pgsql-general@postgresql.org Subject: Re: Re: Data type for storing images? In-reply-to: <000e01c0aba1$0438f5a0$800010ac@localdomain> References: <20010311223818.18682.qmail@mailhost.sidereal.kz> <20010311223818.18682.qmail@mailhost.sidereal.kz> <3.0.5.32.20010313153121.009643c0@192.228.128.13> <20010313090044.25147.qmail@mailhost.sidereal.kz> <000e01c0aba1$0438f5a0$800010ac@localdomain> Comments: In-reply-to "Gordan Bobic" message dated "Tue, 13 Mar 2001 09:35:59 +0000" Date: Tue, 13 Mar 2001 13:25:56 -0500 Message-ID: <20505.984507956@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/609 X-Sequence-Number: 6120 "Gordan Bobic" writes: > More to the point, what would be a reason for not using bytea to > replace BLOBs completely? The fact that encoding/decoding is a pain in the neck :-(. The lo_read/lo_write interfaces are a relatively convenient way to send and receive binary data, but the ASCII input-output representation that bytea uses is not. We really need some binary-friendly data transmission interface like lo_read/lo_write for bytea fields before they will be ready to take over the world. I think Jan has some ideas about how to do that, but it's not done yet. regards, tom lane