Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 66E24475A04 for ; Fri, 10 May 2002 10:14:47 -0400 (EDT) Received: from shire.ontko.com (shire.ontko.com [199.164.165.1]) by postgresql.org (Postfix) with ESMTP id 1604547626A for ; Fri, 10 May 2002 10:13:19 -0400 (EDT) Received: from nick (bilbo.ontko.com [199.164.165.101]) by shire.ontko.com (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id JAA09582; Fri, 10 May 2002 09:13:22 -0500 X-Authentication-Warning: shire.ontko.com: Host bilbo.ontko.com [199.164.165.101] claimed to be nick Reply-To: From: "Nick Fankhauser" To: "pgsql-admin" Cc: "Ray Ontko" Subject: A couple of errors encountered in 7.1.3=>7.2.1-2 data migration Date: Fri, 10 May 2002 09:11:57 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Archive-Number: 200205/78 X-Sequence-Number: 4253 Hi- The background info: Debian 2.4.14 on both source & destination boxes PostgreSQL 7.1.3 on source PostgreSQL 7.2.1-2 on destination We are testing 7.2 with our application by installing it on a separate box & accessing it via the network. The 7.2 install is just a plain vanilla install using the Debian package which went well. (Well done, as usual Oliver!) The export of data from the old system was simply a pg_dumpall, and the import was a load of the dump file using psql and an empty newly created database. The load returned two errors that I don't understand: (1) ERROR: DefineIndex: index function must be marked iscachable unfortunately, I don't know which line of the dumpfile we were on when this occurred, but It only happened once, and the only indexes I can think of that might be different from the rest are functional indexes. One of them is an index on upper(field), and the other is based on a function defined in psql that uses the translate function. (2) ERROR: cannot find attribute 1 of relation schedule_notification_log ERROR: cannot find attribute 1 of relation schedule_notification_log We got this one twice, just as shown above. When I do a \d schedule_notification_log, I get this result: develop=# \d schedule_notification_log Table "schedule_notification_log" Column | Type | Modifiers --------+------+----------- Other than these errors, the data migration went very smoothly, and our applications have functioned at least partially without modification. We haven't been able to test thoroughly yet, because a few queries are very slow, and the second error above seems to keep vacuum analyze from running as well. Any thoughts on these errors are appreciated. Regards, -Nick -------------------------------------------------------------------------- Nick Fankhauser nickf@ontko.com Phone 1.765.935.4283 Fax 1.765.962.9788 Ray Ontko & Co. Software Consulting Services http://www.ontko.com/