From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: BYTEA |
Date: | 2016-01-18 10:05:07 |
Message-ID: | 20160118100507.GA23017@hermes.hilbert.loc |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Joseph Krogh | 2016-01-18 13:06:55 | Re: BYTEA |
Previous Message | Cat | 2016-01-18 00:25:43 | Re: BYTEA |