Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aI9PI-0003ER-Ie for pgsql-sql@arkaria.postgresql.org; Sun, 10 Jan 2016 06:23:17 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aI9PI-0004iG-4d for pgsql-sql@arkaria.postgresql.org; Sun, 10 Jan 2016 06:23:16 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aI9PG-0004i5-2M for pgsql-sql@postgresql.org; Sun, 10 Jan 2016 06:23:14 +0000 Received: from nm45.bullet.mail.gq1.yahoo.com ([67.195.87.147]) by makus.postgresql.org with esmtps (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aI9P8-0006Z7-6C for pgsql-sql@postgresql.org; Sun, 10 Jan 2016 06:23:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s2048; t=1452406984; bh=suvGX79T09kn77DaPFBQ5yXBIWPQEKD7tnGxrDjigJQ=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=JuZFwQA9cudgnq4tr1es3zLJBmoiBvqxYhpY9IUWIhNihbSFGInUqOOzhgis76F+7m9BFnd8rdGUzmq6EhhyyxCQUQJkHuI+qOBJrgf+IUhc46lA2dgPvFQpQYRkNWXV9jlSsBUnpAg+DW74Tg0/sLAPwSdlQh0+5eJYhQZSuEw1vfTHw68HNLwC86FgVGiI7fnBblFpk8yszzW+X5e0ujjeAZS1rWdB/VrVuFfLdrSp8KVvKPwfh+6Ujnryns62MgJEEyyh717F1UfAe9dkjjTTy6PaOs8kps5j7OJC7lLMGpGlYuIJ6XHhmjKJujNQ4lCuYWid32kIS4pLmMDe6Q== Received: from [127.0.0.1] by nm45.bullet.mail.gq1.yahoo.com with NNFMP; 10 Jan 2016 06:23:04 -0000 Received: from [98.137.12.59] by nm45.bullet.mail.gq1.yahoo.com with NNFMP; 10 Jan 2016 06:20:03 -0000 Received: from [66.196.81.172] by tm4.bullet.mail.gq1.yahoo.com with NNFMP; 10 Jan 2016 06:20:03 -0000 Received: from [98.139.215.249] by tm18.bullet.mail.bf1.yahoo.com with NNFMP; 10 Jan 2016 06:20:03 -0000 Received: from [127.0.0.1] by omp1062.mail.bf1.yahoo.com with NNFMP; 10 Jan 2016 06:20:03 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 341082.61811.bm@omp1062.mail.bf1.yahoo.com X-YMail-OSG: IbWjU.0VM1nn0eyAaL7NcXiMTouMFS8DejNAHrUwXUmRS8IyMlHTZ6uolq9B8vh _vCXIpSVhI21pIR7SCzreVSrkMycBbQiLriWFI9rX2vxb2LrzYVbDexGx915CP9r.z.8sF4ffCAS uDNJCq5zYQ4iG1m7Jsu2BESpdSvdi5KsGc0F7ke7.QQiXOLaKj5wWkVWmI6WYWiN_EfJmKn5x9li nwsMm_0yuU2ITNcgx9QGUJKfKmZBMgukPthWsnBCy8oAxcHgNzYh7dh6HuvOQAlu.TPnphBjBYTL a668deiRidrsmC5Ato9vj8PRU0Q1IY0KBujReZwTyDfr_RXFiC_H27ibQuV1OHqnXutWOqUB72pX KnSmhLfxOo2ijzoHIyDLZdm6yfPcyc6iOHdQI7p7zm_17wT0V_aB_UB_l11y5FjvirKDUlAC.2RG h7wZuDcxHFlZwUqKtRTMTfQpFoFZ_Oqq3s5kOZU.1FWuimJJUIqMlw6QBp85CRNqX7X31sxPS0JC koT3BdERmI0vhupBSuH5euNmFXKzNMKgLChL9kBVFDPo- Received: by 76.13.27.134; Sun, 10 Jan 2016 06:20:02 +0000 Date: Sun, 10 Jan 2016 06:20:02 +0000 (UTC) From: Eugene Yin Reply-To: Eugene Yin To: "pgsql-sql@postgresql.org" Message-ID: <21791464.2842310.1452406802668.JavaMail.yahoo@mail.yahoo.com> Subject: BLOBs MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2842309_440031746.1452406802666" References: <21791464.2842310.1452406802668.JavaMail.yahoo.ref@mail.yahoo.com> Content-Length: 7399 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org ------=_Part_2842309_440031746.1452406802666 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The following statement is excerpted from the=C2=A0 "Oracle to Postgres Conversion" https://wiki.postgresql.org/wiki/Oracle_to_Postgres_Conversion#Grammar_Diff= erences on=C2=A0Postgres 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 u= p 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 su= pport, by uuencoding/decoding binary files before stuffing them into or ext= racting them from the database. The resulting objects can be consistently d= umped by "pg_dump" while the RDBMS is up and running. There is no need to i= nterrupt 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 encode= d data into 8K chunks.Postgres large objects are scheduled for a major over= haul in summer 2000. Because of this, only the BLOB functionality used by t= he ACS was implemented. Now for Postgres 9.4.5, =C2=A0is backup of the BLOB still an issue as descr= ibed above, OR, it now works equivalent to that of Oracle? Thanks Eugene ------=_Part_2842309_440031746.1452406802666 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The following statem= ent is excerpted from the 

"Oracle to P= ostgres Conversion"



on Postgres 8.4.


BLOBs

Bin= ary 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 knoc= k 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/d= ecoding binary files before stuffing them into or extracting them from the = database. The resulting objects can be consistently dumped by "pg_dump" whi= le 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.
Pos= tgres large objects are scheduled for a major overhaul in summer 2000. Beca= use of this, only the BLOB functionality used by the ACS was implemented.


Now for Postgre= s 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
------=_Part_2842309_440031746.1452406802666--