Re: BLOB support
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Radosław Smogura <rsmogura@softperience.eu>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter_e@gmx.net>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-02T17:43:16Z
Lists: pgsql-hackers
=?utf-8?q?Rados=C5=82aw_Smogura?= <rsmogura@softperience.eu> writes: > Tom Lane <tgl@sss.pgh.pa.us> Thursday 02 of June 2011 16:42:42 >> Yes. I think the appropriate problem statement is "provide streaming >> access to large field values, as an alternative to just fetching/storing >> the entire value at once". I see no good reason to import the entire >> messy notion of LOBS/CLOBS. (The fact that other databases have done it >> is not a good reason.) > In context of LOBs streaming is resolved... I use current LO functionallity > (so driver may be able to read LOBs as psql \lo_export does it or using COPY > subprotocol) and client should get just LO's id. Just to be clear: I do not want to expose a concept of object IDs for field values in the first place. All of the problems you enumerate stem from the idea that LOBs ought to be a distinct kind of field, and I don't buy that. regards, tom lane