Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id B704D9FA5CC for ; Fri, 26 Oct 2007 03:08:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 13122-06 for ; Fri, 26 Oct 2007 03:07:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from weatherbeeta.com.au (218-214-212-153.people.net.au [218.214.212.153]) by postgresql.org (Postfix) with ESMTP id ACF019F9697 for ; Fri, 26 Oct 2007 03:07:55 -0300 (ADT) Received: (qmail 28443 invoked from network); 26 Oct 2007 06:07:52 -0000 X-NetworkBox-HamSign: 0101;OUT;wbeetaau1;d641cff6f28b616f4a31e7f4f49168ca; Received: from unknown (HELO mail.weatherbeeta.com.au) (10.20.0.2) by 10.20.0.254 with SMTP; 26 Oct 2007 06:07:52 -0000 Received: (qmail 16702 invoked by uid 1166); 26 Oct 2007 16:07:44 +1000 Received: from 172.20.0.155 by mail.weatherbeeta.com.au (envelope-from , uid 1165) with qmail-scanner-1.25-st-qms (clamdscan: 0.88.6/2315. perlscan: 1.25-st-qms. Clear:RC:1(172.20.0.155):. Processed in 1.004264 secs); 26 Oct 2007 06:07:44 -0000 X-Antivirus-mail.weatherbeeta.com.au-Mail-From: phillip.smith@weatherbeeta.com.au via mail.weatherbeeta.com.au X-Antivirus-mail.weatherbeeta.com.au: 1.25-st-qms (Clear:RC:1(172.20.0.155):. Processed in 1.004264 secs Process 16691) Received: from it-phil.weatherbeeta.com.au (HELO wbaus090) (172.20.0.155) by mail.weatherbeeta.com.au with SMTP; 26 Oct 2007 16:07:40 +1000 From: "Phillip Smith" To: "'David Young'" , Subject: Re: 32-bit to 64-bit migration screwup Date: Fri, 26 Oct 2007 16:07:46 +1000 Organization: Weatherbeeta Pty Ptd Message-ID: <011601c81796$874071e0$9b0014ac@wbaus090> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0117_01C817EA.58EC81E0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 In-Reply-To: Importance: Normal X-Scanned-By-wbeetaau1: Virus scan performed by network-box X-Scanned-By-wbeetaau1: Scanner file id is wbeetaau1-1193378872.186-28437-000 X-Scanned-By-wbeetaau1: No known viruses found in message (received+scanned in 0.03/0.06 secs) X-Scanned-By-wbeetaau1: Spam-Check-Result: No, hits=0 required=7 tests= autolearn=no version=2.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/260 X-Sequence-Number: 27174 This is a multi-part message in MIME format. ------=_NextPart_000_0117_01C817EA.58EC81E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm assuming you've made a jump in database version - ie, 7.4 to 8.2 or similar. =20 You need to use initdb to create new database files, then pg_dumpall on = the old system to dump the data out of the old before importing to the new. = Make sure you use pg_dumpall from the new version to dump the data from the = old database. =20 -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of David Young Sent: Friday, 26 October 2007 15:52 To: pgsql-admin@postgresql.org Subject: [ADMIN] 32-bit to 64-bit migration screwup =20 All, =20 I was hoping someone can help me fix a big blunder. I recently bought a = new system to replace the old one. The new system is running 64bit linux = and the old one 32bit. I installed PG 64-bit and tried to bring the old database back up. Even though I'm running the same version of PG, it is giving me an error when I try to start it back up. below is the message from pgstartup.log. It looks like it doesn't recognize the control file anymore. =20 Am I screwed? I don't have the old system anymore and I didn't do a = dump. I figure if I'm running the same version of PG, the data will come back = up correctly. If someone can help me out of this jam, I would greatly appreciate it.=20 =20 Thanks, David =20 ------------------pgstartup.log--------------- The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale en_US.UTF-8. The default database encoding has accordingly been set to UTF8. fixing permissions on existing directory /var/lib/pgsql/data ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers/max_fsm_pages ... 24MB/153600 creating configuration files ... ok=20 creating template1 database in /var/lib/pgsql/data/base/1 ... ok initializing pg_authid ... ok initializing dependencies ... ok creating system views ... ok loading system objects' descriptions ... ok creating conversions ... ok setting privileges on built-in objects ... ok creating information schema ... ok vacuuming database template1 ... ok copying template1 to template0 ... ok copying template1 to postgres ... ok=20 Success. You can now start the database server using: /usr/bin/postgres -D /var/lib/pgsql/data or /usr/bin/pg_ctl -D /var/lib/pgsql/data -l logfile start LOG: logger shutting down LOG: logger shutting down LOG: logger shutting down LOG: logger shutting down LOG: logger shutting down FATAL: incorrect checksum in control file FATAL: incorrect checksum in control file=20 FATAL: incorrect checksum in control file =0ATHINK BEFORE YOU PRINT - Save paper if you don't really need to print this= =0A=0A*******************Confidentiality and Privilege Notice*******************= =0A=0AThe material contained in this message is privileged and confidential to= =0Athe addressee. If you are not the addressee indicated in this message or= =0Aresponsible for delivery of the message to such person, you may not copy=0Aor= deliver this message to anyone, and you should destroy it and kindly=0Anotify= the sender by reply email.=0A=0AInformation in this message that does not relat= e to the official business=0Aof Weatherbeeta must be treated as neither given = nor endorsed by Weatherbeeta.=0AWeatherbeeta, its employees, contractors or as= sociates shall not be liable=0Afor direct, indirect or consequential loss aris= ing from transmission of this=0Amessage or any attachments=0Ae-mail.=0A ------=_NextPart_000_0117_01C817EA.58EC81E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m assuming you’ve = made a jump in database version – ie, 7.4 to 8.2 or = similar…

 

You need to use initdb to create = new database files, then pg_dumpall on the old system to dump the data out = of the old before importing to the new. Make sure you use pg_dumpall from the = new version to dump the data from the old database.

 

-----Original Message-----
From: pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of David Young
Sent: Friday, 26 October = 2007 15:52
To: = pgsql-admin@postgresql.org
Subject: [ADMIN] 32-bit = to 64-bit migration screwup

 

All,

 

I was hoping someone can help me fix a big blunder.  I = recently bought a new system to replace the old one.  The new system is = running 64bit linux and the old one 32bit.  I installed PG 64-bit and = tried to bring the old database back up.  Even though I'm running the = same version of PG, it is giving me an error when I try to start it back = up.  below is the message from pgstartup.log.  It looks like it doesn't recognize the control file anymore.

 

Am I screwed?  I don't have the old system anymore and I = didn't do a dump.  I figure if I'm running the same version of PG, the data = will come back up correctly.  If someone can help me out of this jam, I = would greatly appreciate it.

 

Thanks,

David

 

------------------pgstartup.log---------------

The files belonging to this database system will be owned by user = "postgres".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to = UTF8.

fixing permissions on existing directory /var/lib/pgsql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 24MB/153600
creating configuration files ... ok
creating template1 database in /var/lib/pgsql/data/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok

Success. You can now start the database server using:

    /usr/bin/postgres -D /var/lib/pgsql/data
or
    /usr/bin/pg_ctl -D /var/lib/pgsql/data -l logfile = start

LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
FATAL:  incorrect checksum in control file
FATAL:  incorrect checksum in control file
FATAL:  incorrect checksum in control file


=

=0ATHINK BEFORE YOU PRINT - Save paper if you don't really need to print t= his e-mail.=0A

=0A*******************Confidentiality and Privilege Notice**= *****************=0A

=0AThe material contained in this message is privileg= ed and confidential to=0Athe addressee. If you are not the addressee indicate= d in this message or=0Aresponsible for delivery of the message to such person,= you may not copy=0Aor deliver this message to anyone, and you should destroy = it and kindly=0Anotify the sender by reply email.=0A

=0AInformation in this mess= age that does not relate to the official business=0Aof Weatherbeeta must be tr= eated as neither given nor endorsed by Weatherbeeta.=0AWeatherbeeta, its emplo= yees, contractors or associates shall not be liable=0Afor direct, indirect or = consequential loss arising from transmission of this=0Amessage or any attachme= nts=0A
= ------=_NextPart_000_0117_01C817EA.58EC81E0--