From matt@luggagepros.com Wed Mar 10 16:47:39 2010 Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id EB029635A6D for ; Wed, 10 Mar 2010 12:47:39 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 17121-06 for ; Wed, 10 Mar 2010 16:47:28 +0000 (UTC) X-Greylist: delayed 00:17:51.766042 by SQLgrey-1.7.6 Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mail.postgresql.org (Postfix) with ESMTP id 915B36328BA for ; Wed, 10 Mar 2010 12:47:27 -0400 (AST) Received: from Matt (c-75-72-80-156.hsd1.mn.comcast.net [75.72.80.156]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id o2AGTYY9022812 for ; Wed, 10 Mar 2010 08:29:34 -0800 From: "Matt Janssen" To: Subject: pg_dump / pg_restore with Large Objects from 32-bit to 64-bit Date: Wed, 10 Mar 2010 10:29:18 -0600 Organization: Luggage Pros Message-ID: <000301cac06e$d54d9f10$7fe8dd30$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01CAC03C.8AB32F10" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcrAbtSzVsujnI4RQ7y95+QHuz+HNA== Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.184 tagged_above=-10 required=5 tests=BAYES_40=-0.185, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201003/97 X-Sequence-Number: 33896 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

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=3Dc --blobs = --file=3Dbackup.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-- From tgl@sss.pgh.pa.us Mon Mar 15 20:54:39 2010 Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id A00AF65A030 for ; Mon, 15 Mar 2010 17:54:39 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 22962-01 for ; Mon, 15 Mar 2010 20:54:28 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 6A3A865A116 for ; Mon, 15 Mar 2010 16:58:19 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o2FJwD1S022706; Mon, 15 Mar 2010 15:58:13 -0400 (EDT) To: "Matt Janssen" cc: pgsql-admin@postgresql.org Subject: Re: pg_dump / pg_restore with Large Objects from 32-bit to 64-bit In-reply-to: <000301cac06e$d54d9f10$7fe8dd30$@com> References: <000301cac06e$d54d9f10$7fe8dd30$@com> Comments: In-reply-to "Matt Janssen" message dated "Wed, 10 Mar 2010 10:29:18 -0600" Date: Mon, 15 Mar 2010 15:58:13 -0400 Message-ID: <22705.1268683093@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/101 X-Sequence-Number: 33900 "Matt Janssen" 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