undefined | Better HN

0 pointspilif14y ago0 comments

Nope. There was blob-support, but that relied on special library functions to extract the data to a file which you'd then have to manually read.

Of course this also means that you couldn't search in these fields or do anything else you'd do directly on the database.

TOAST tables were added in 7.1 AFAIK which lifted that limit and allowed for arbitrary sized rows by moving the big fields away into their own storage.

The old functionality is still there (http://www.postgresql.org/docs/9.0/interactive/largeobjects....) though I totally failed and still fail to see any practical use.

0 comments

masklinn14y ago

> Nope. There was blob-support, but that relied on special library functions to extract the data to a file which you'd then have to manually read.

OK.

> The old functionality is still there (http://www.postgresql.org/docs/9.0/interactive/largeobjects....) though I totally failed and still fail to see any practical use.

Memory constraints maybe? That's about the only justification I could see for using that over bytea: if you store single binary objects in the GB+ range, you may want to interact with them as streams.

j / k navigate · click thread line to collapse