agora inbox for pgsql-sql@postgresql.org  
help / color / mirror / Atom feed
From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-sql@postgresql.org
Subject: Re: BYTEA
Date: Mon, 18 Jan 2016 11:05:07 +0100
Message-ID: <20160118100507.GA23017@hermes.hilbert.loc> (raw)
In-Reply-To: <20160118002543.GC11533@zip.com.au>
References: <194527298.6807703.1453059218766.JavaMail.yahoo.ref@mail.yahoo.com>
	<194527298.6807703.1453059218766.JavaMail.yahoo@mail.yahoo.com>
	<20160118002543.GC11533@zip.com.au>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>

On Mon, Jan 18, 2016 at 11:25:43AM +1100, Cat wrote:

> 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?

It would certainly be of use to add that option to the aforementioned wiki page.

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


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



view thread (17+ messages)  latest in thread

Message-ID: <20160118100507.GA23017@hermes.hilbert.loc>
Permalink:  ../20160118100507.GA23017@hermes.hilbert.loc/
Also on:    postgresql.org/message-id/20160118100507.GA23017@hermes.hilbert.loc

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: Karsten.Hilbert@gmx.net
  Subject: Re: BYTEA
  In-Reply-To: <20160118100507.GA23017@hermes.hilbert.loc>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox