Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id DFEA22E027E for ; Mon, 3 Mar 2008 16:45:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15527-03 for ; Mon, 3 Mar 2008 16:45:02 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from exchange.DOCS.COM (exchange.docs.com [75.13.188.5]) by postgresql.org (Postfix) with ESMTP id 2E0C42E0260 for ; Mon, 3 Mar 2008 16:45:01 -0400 (AST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: Error restoring after 8.3 upgrade Date: Mon, 3 Mar 2008 14:22:36 -0600 Message-ID: <52F2AD70C422474B857FC9E3F7B62539027C886A@exchange.DOCS.COM> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Error restoring after 8.3 upgrade Thread-Index: Ach9bFHdL7JWvJK6QbSMQ1kZzqlvKw== From: "Ryan Wells" To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.189 tagged_above=0 required=5 tests=AWL=1.189 X-Spam-Level: * X-Archive-Number: 200803/16 X-Sequence-Number: 28499 We have a database that we're upgrading from 8.2 to 8.3. Our basic prodecure is to make a backup of the data using pgAdmin, remove 8.2, install 8.3, then use pgAdmin to restore the data. That works fine on our test system, but on the actual server we get the following error during the restore: =20 pg_restore: [archiver (db)] error returned by PQputCopyData: could not send data to server: No buffer space available (0x00002747/10055) pg_restore: *** aborted because of error Our support staff says the server OS is Windows Server 2003, but they don't have the other machine specs documented. I'm trying to get those details. =20 Google turned up a few discussions of similar errors that may be related, but no certain fixes: http://archives.postgresql.org/pgsql-general/2006-01/msg00769.php http://archives.postgresql.org/pgsql-bugs/2006-07/msg00051.php http://archives.postgresql.org/pgsql-bugs/2006-04/msg00260.php http://archives.postgresql.org/pgsql-general/2006-01/msg00328.php http://www.webservertalk.com/archive307-2007-3-1832662.html http://osdir.com/ml/db.postgresql.ports/2005-11/msg00000.html http://www.mail-archive.com/pgsql-bugs@postgresql.org/msg15449.html We've tried adjusting the buffer sizes in postgresql.conf and the Windows registry tweak that one site suggested, but neither of those made any apparent difference. =20 Naturally I'm hoping this is a common, well-known issue with an easy fix, but of course I don't expect that to be the case. :-) Thanks, Ryan