BLOBs

The following statement is excerpted from the 

"Oracle to Postgres Conversion"

https://wiki.postgresql.org/wiki/Oracle_to_Postgres_Conversion#Grammar_Differences

on Postgres 8.4.

BLOBs
Binary large object support in Postgres is very poor and unsuitable for use in a 24/7 environment, because you can't dump them with pg_dump. Backing up a database that makes use of Postgres large objects requires one to knock down the RDBMS and dump the files in the database directory.Don Baccus put together a hack that extends AOLserver's postgres driver with BLOB-like support, by uuencoding/decoding binary files before stuffing them into or extracting them from the database. The resulting objects can be consistently dumped by "pg_dump" while the RDBMS is up and running. There is no need to interrupt service while making your backup.To get around the one-block limit on the size of a tuple imposed by Postgres, the driver segments the encoded data into 8K chunks.Postgres large objects are scheduled for a major overhaul in summer 2000. Because of this, only the BLOB functionality used by the ACS was implemented.

Now for Postgres 9.4.5,  is backup of the BLOB still an issue as described above, OR, it now works equivalent to that of Oracle?

Thanks

Eugene