| From: | Cat <cat(at)zip(dot)com(dot)au> |
|---|---|
| To: | Eugene Yin <eugeneymail(at)ymail(dot)com> |
| Cc: | Postgres List <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: BYTEA |
| Date: | 2016-01-18 00:25:43 |
| Message-ID: | 20160118002543.GC11533@zip.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2016-01-18 10:05:07 | Re: BYTEA |
| Previous Message | Thomas Kellerer | 2016-01-17 22:17:29 | Re: BLOBs |