BLOBs - Mailing list pgsql-sql
From | Eugene Yin |
---|---|
Subject | BLOBs |
Date | |
Msg-id | 21791464.2842310.1452406802668.JavaMail.yahoo@mail.yahoo.com Whole thread Raw |
Responses |
Re: BLOBs
|
List | pgsql-sql |
<div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande,sans-serif;font-size:13px"><h2 class="" id="yui_3_16_0_1_1452227859253_99029" style="color: rgb(230, 86, 0); font-weight:normal; margin-top: 0px; margin-bottom: 0.6em; padding-top: 0.5em; padding-bottom: 0.17em; border-bottom-width:1px; border-bottom-style: solid; border-bottom-color: rgb(170, 170, 170); font-size: 19.0499992370605px;font-family: sans-serif; line-height: 19.0499992370605px; background-image: none; background-attachment:initial; background-size: initial; background-origin: initial; background-clip: initial; background-position:initial; background-repeat: initial;"><span class="" id="yui_3_16_0_1_1452227859253_99130">The followingstatement is excerpted from the </span></h2><h1 class="" id="yui_3_16_0_1_1452227859253_99133" style="color: rgb(230,86, 0); font-weight: normal; margin-top: 0px; margin-bottom: 0.1em; padding-top: 0.5em; padding-bottom: 0.17em; border-bottom-width:1px; border-bottom-style: solid; border-bottom-color: rgb(170, 170, 170); font-size: 23.8759994506836px;font-family: sans-serif; line-height: 19.0499992370605px; background: none;">"Oracle to Postgres Conversion"</h1><divid="yui_3_16_0_1_1452227859253_99134"><span class=""><br /></span></div><div dir="ltr" id="yui_3_16_0_1_1452227859253_99078"><spanclass="" id="yui_3_16_0_1_1452227859253_99077"><a href="https://wiki.postgresql.org/wiki/Oracle_to_Postgres_Conversion#Grammar_Differences" id="yui_3_16_0_1_1452227859253_99074">https://wiki.postgresql.org/wiki/Oracle_to_Postgres_Conversion#Grammar_Differences</a><br /></span></div><divid="yui_3_16_0_1_1452227859253_99078"><br /></div><div dir="ltr" id="yui_3_16_0_1_1452227859253_99078">on <spanclass="" id="yui_3_16_0_1_1452227859253_99196" style="font-family: sans-serif;font-size: 12.6999998092651px; line-height: 19.0499992370605px;">Postgres 8.4.</span></div><div dir="ltr" id="yui_3_16_0_1_1452227859253_99078"><spanclass="" style="font-family: sans-serif; font-size: 12.6999998092651px; line-height:19.0499992370605px;"><br /></span></div><div dir="ltr" id="yui_3_16_0_1_1452227859253_99078"><br /></div><h2class="" id="yui_3_16_0_1_1452227859253_99029" style="color: rgb(230, 86, 0); font-weight: normal; margin-top:0px; margin-bottom: 0.6em; padding-top: 0.5em; padding-bottom: 0.17em; border-bottom-width: 1px; border-bottom-style:solid; border-bottom-color: rgb(170, 170, 170); font-size: 19.0499992370605px; font-family: sans-serif;line-height: 19.0499992370605px; background-image: none; background-attachment: initial; background-size: initial;background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"><spanclass="" id="BLOBs">BLOBs</span></h2><div class="" id="yui_3_16_0_1_1452227859253_99032" style="margin-top:0.4em; margin-bottom: 0.5em; line-height: 19.0499992370605px; font-family: sans-serif; font-size: 12.6999998092651px;"><bid="yui_3_16_0_1_1452227859253_99194">Binary large object support in Postgres is very poor and unsuitablefor use in a 24/7 environment</b>, because you can't dump them with pg_dump. Backing up a database that makes useof Postgres large objects requires one to knock down the RDBMS and dump the files in the database directory.</div><divclass="" id="yui_3_16_0_1_1452227859253_99034" style="margin-top: 0.4em; margin-bottom: 0.5em; line-height:19.0499992370605px; font-family: sans-serif; font-size: 12.6999998092651px;">Don Baccus put together a hack thatextends AOLserver's postgres driver with BLOB-like support, by uuencoding/decoding binary files before stuffing theminto or extracting them from the database. The resulting objects can be consistently dumped by "pg_dump" while the RDBMSis up and running. There is no need to interrupt service while making your backup.</div><div class="" id="yui_3_16_0_1_1452227859253_99036"style="margin-top: 0.4em; margin-bottom: 0.5em; line-height: 19.0499992370605px; font-family:sans-serif; font-size: 12.6999998092651px;">To get around the one-block limit on the size of a tuple imposedby Postgres, the driver segments the encoded data into 8K chunks.</div><div class="" id="yui_3_16_0_1_1452227859253_99038"style="margin-top: 0.4em; margin-bottom: 0.5em; line-height: 19.0499992370605px; font-family:sans-serif; font-size: 12.6999998092651px;"><b id="yui_3_16_0_1_1452227859253_99170">Postgres large objects arescheduled for a major overhaul in summer 2000. Because of this, only the BLOB functionality used by the ACS was implemented.</b></div><divclass="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040"><br class="" id="yui_3_16_0_1_1452227859253_99042"/></div><div class="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040"><br /></div><divclass="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040">Now for Postgres 9.4.5, is backup of the BLOB stillan issue as described above, OR, it now works equivalent to that of Oracle?</div><div class="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040"><br/></div><div class="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040"><br /></div><divclass="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040">Thanks</div><div class="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040"><br/></div><div class="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040"><br /></div><divclass="" dir="ltr" id="yui_3_16_0_1_1452227859253_99040">Eugene</div></div>