Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id B0135CE6EB for ; Fri, 15 Jun 2012 05:25:01 -0300 (ADT) Received: from adsltrust.ath.forthnet.gr ([194.219.204.174] helo=smadev.internal.net) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SfRpz-0007q0-C2 for pgsql-sql@postgresql.org; Fri, 15 Jun 2012 08:25:00 +0000 Received: from smadev.internal.net (localhost [127.0.0.1]) by smadev.internal.net (8.14.5/8.14.5) with ESMTP id q5F8OjjV033309; Fri, 15 Jun 2012 11:24:45 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) Received: (from achill@localhost) by smadev.internal.net (8.14.5/8.14.5/Submit) id q5F8OjJa033308; Fri, 15 Jun 2012 11:24:45 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) X-Authentication-Warning: smadev.internal.net: achill set sender to achill@matrix.gatewaynet.com using -f From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: Scott Marlowe Subject: Re: Insane behaviour in 8.3.3 Date: Fri, 15 Jun 2012 11:24:44 +0300 User-Agent: KMail/1.13.7 (FreeBSD/8.3-RELEASE; KDE/4.7.3; amd64; ; ) References: <201206141139.35601.achill@matrix.gatewaynet.com> <201206151025.32973.achill@matrix.gatewaynet.com> In-Reply-To: Cc: pgsql-sql@postgresql.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201206151124.45021.achill@matrix.gatewaynet.com> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201206/40 X-Sequence-Number: 36694 On =CE=A0=CE=B1=CF=81 15 =CE=99=CE=BF=CF=85=CE=BD 2012 10:28:20 Scott Marlo= we wrote: > You do realize you're missing four years of bug fixes right? On =CE=A0=CE=B5=CE=BC 14 =CE=99=CE=BF=CF=85=CE=BD 2012 11:39:35 Achilleas M= antzios wrote: > Unfortunately the remote installations are neither physically accessible > nor by TCP/IP accesible (comms are done via UUCP and administration via > minicom, and the costs are just huge 5 USD/min for 33Kbits/sec). So, i > would exhaust all posibilities before deciding to ship a new postgresql > version there, and remotely upgrade, physically travel to the ship or even > trying to do a backup/initdb/restore in the existing version. Any help > would be really really appreciated. >=20 > Also, as you might have understood, upgrading, although generally a good > idea, does not apply so easily in our case. And i forgot to mention, minicom term emulation quality sucks, even giving = simple shell commands is a PITA, upgrading the whole fleet would mean bast case sc= enario minimum 21K USD for the whole fleet + suspension of all other activities fo= r two months. If physical travel was involved, the cost would be increased at even higher= levels. =2D Achilleas Mantzios IT DEPT