Received: from mail1.expertrade.com (r87-43-dsl.sea.lightrealm.net [216.122.43.87]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2C2Cfx38590 for ; Sun, 11 Mar 2001 21:12:42 -0500 (EST) (envelope-from d.wall@computer.org) Received: from reggae (reggae.expertrade.com [216.122.43.90]) by mail1.expertrade.com (8.9.3/8.9.3) with SMTP id SAA07030; Sun, 11 Mar 2001 18:15:50 -0800 Message-ID: <001701c0aa99$e419fb00$5a2b7ad8@expertrade.com> Reply-To: "David Wall" From: "David Wall" To: , "Tom Lane" Cc: References: <20010311223818.18682.qmail@mailhost.sidereal.kz> <23574.984361701@sss.pgh.pa.us> Subject: Re: Data type for storing images? Date: Sun, 11 Mar 2001 18:12:29 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Archive-Number: 200103/492 X-Sequence-Number: 5978 > bytea is probably your best bet. The 8k limit is toast in 7.1, btw. If you're using JDBC, you may not be able to get bytea types to work. I was able to get the SQL type OID to work with JDBC's get/setBytes() methods. You may also want to use 7.1 since I believe it's large object support is improved. David