pg_dump / pg_restore with Large Objects from 32-bit to 64-bit

This is a multi-part message in MIME format.

------=_NextPart_000_0004_01CAC03C.8AB32F10
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

When migrating our Postgres databases from 32 to 64-bit systems, including
large binary objects, how well will this work?



32-bit server) pg_dump --format=c --blobs --file=backup.pg mydb



64-bit server) pg_restore -d mydb backup.pg



I'm hoping that PG's compressed custom archive format is not architecture
dependant. Thanks!


------=_NextPart_000_0004_01CAC03C.8AB32F10
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
[at] font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
[at] font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
..MsoChpDefault
{mso-style-type:export-only;}
[at] page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>When migrating our Postgres databases from 32 to =
64-bit
systems, including large binary objects, how well will this =
work?<o:p></o:p></p>

<p class=3DMsoNormal><o:p> </o:p></p>

<p class=3DMsoNormal>32-bit server) pg_dump --format=3Dc --blobs =
--file=3Dbackup.pg
mydb<o:p></o:p></p>

<p class=3DMsoNormal><o:p> </o:p></p>

<p class=3DMsoNormal>64-bit server) pg_restore -d mydb =
backup.pg<o:p></o:p></p>

<p class=3DMsoNormal><o:p> </o:p></p>

<p class=3DMsoNormal>I’m hoping that PG’s compressed custom =
archive
format is not architecture dependant. Thanks!<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0004_01CAC03C.8AB32F10--
Matt Janssen [ Mi, 10 März 2010 17:29 ] [ ID #2035081 ]

Re: pg_dump / pg_restore with Large Objects from 32-bit to 64-bit

"Matt Janssen" <matt [at] luggagepros.com> writes:
> When migrating our Postgres databases from 32 to 64-bit systems, including
> large binary objects, how well will this work?

> 32-bit server) pg_dump --format=c --blobs --file=backup.pg mydb
> 64-bit server) pg_restore -d mydb backup.pg

Should be fine; but remember that only gets you the contents of the one
database. You may also want pg_dumpall --globals-only to transfer
role properties and such.

> I'm hoping that PG's compressed custom archive format is not architecture
> dependant. Thanks!

It is not.

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Tom Lane [ Mo, 15 März 2010 20:58 ] [ ID #2035085 ]
Datenbanken » gmane.comp.db.postgresql.admin » pg_dump / pg_restore with Large Objects from 32-bit to 64-bit

Vorheriges Thema: how to get notification in front end application when ever postgre DB
Nächstes Thema: Autovac versus manual vac with analyze