Date: Mon, 18 Jan 2016 11:25:43 +1100
From: Cat <cat@zip.com.au>
To: Eugene Yin <eugeneymail@ymail.com>
Cc: Postgres List <pgsql-sql@postgresql.org>
Subject: Re: BYTEA
Message-ID: <20160118002543.GC11533@zip.com.au>
References: 
 <194527298.6807703.1453059218766.JavaMail.yahoo.ref@mail.yahoo.com>
 <194527298.6807703.1453059218766.JavaMail.yahoo@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <194527298.6807703.1453059218766.JavaMail.yahoo@mail.yahoo.com>
Organisation: Furball Inc.
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On Sun, Jan 17, 2016 at 07:33:38PM +0000, Eugene Yin wrote:
> Pg 9.4+
> Storing binary data using bytea or text data types   
>    -  Pluses      
>       -  Storing and Accessing entry utilizes the same interface when accessing any other data type or record. 
>       -  No need to track OID of a "large object" you create
> 
>    -  Minus 
>    
>    -  bytea and text data type both use TOAST (details here)      
>       -  limited to 1G per entry 
>       -  4 Billion (> 2KB) entries per table max.
> 
>    -  Need to escape/encode binary data before sending to DB then do the reverse after retrieving the data 
>    -  Memory requirements on the server can be steep even on a small record set. 
> https://wiki.postgresql.org/wiki/BinaryFilesInDB

Would http://multicorn.org/foreign-data-wrappers/#idfilesystem-foreign-data-wrapper be of greater
use? Not sure if it's r/w or r/o.

-- 
  "A search of his car uncovered pornography, a homemade sex aid, women's 
  stockings and a Jack Russell terrier."
    - http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-1111118083480


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql