Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 7CE886FED3 for ; Tue, 19 Jun 2012 06:18:09 -0300 (ADT) Received: from adsltrust.ath.forthnet.gr ([194.219.204.174] helo=smadev.internal.net) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SguZZ-0005GC-OQ for pgsql-sql@postgresql.org; Tue, 19 Jun 2012 09:18:08 +0000 Received: from smadev.internal.net (localhost [127.0.0.1]) by smadev.internal.net (8.14.5/8.14.5) with ESMTP id q5J9HniK079842 for ; Tue, 19 Jun 2012 12:17:49 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) Received: (from achill@localhost) by smadev.internal.net (8.14.5/8.14.5/Submit) id q5J9HnEL079841 for pgsql-sql@postgresql.org; Tue, 19 Jun 2012 12:17:49 +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: pgsql-sql@postgresql.org Subject: Re: Insane behaviour in 8.3.3 Date: Tue, 19 Jun 2012 12:17:49 +0300 User-Agent: KMail/1.13.7 (FreeBSD/8.3-RELEASE; KDE/4.7.3; amd64; ; ) References: <201206141139.35601.achill@matrix.gatewaynet.com> <201206181136.14782.achill@matrix.gatewaynet.com> In-Reply-To: <201206181136.14782.achill@matrix.gatewaynet.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201206191217.49743.achill@matrix.gatewaynet.com> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201206/55 X-Sequence-Number: 36709 We had another corruption incident on the very same machine, this time in t= he jboss subsystem (a "jar cvf" produced corrupted .jar). IMHO this means faulty RAM/disk. If that is true, then i guess HW sanity checks are even more important than= SW upgrades. On =CE=94=CE=B5=CF=85 18 =CE=99=CE=BF=CF=85=CE=BD 2012 11:36:14 you wrote: > Thanx, well said, and especially after this incident we should very well > consider seriously an upgrade. >=20 > On =CE=A0=CE=B1=CF=81 15 =CE=99=CE=BF=CF=85=CE=BD 2012 19:59:05 Scott Mar= lowe wrote: > > Well, I'd see about finding a way to upgrade to 8.3.19. 8.3.3 has > > know data eating bugs. > >=20 > > On Fri, Jun 15, 2012 at 9:32 AM, Achilleas Mantzios > >=20 > > wrote: > > > On =CE=A0=CE=B1=CF=81 15 =CE=99=CE=BF=CF=85=CE=BD 2012 18:03:26 Scott= Marlowe wrote: > > >> Not talking about going to something after 8.3.19, just updating to > > >> the latest 8.3 version. On most systems it's a simple: > > >>=20 > > >> sudo apt-get upgrade > > >>=20 > > >> or similar and sit back and watch. > > >=20 > > > Thanx, unfortunately we dont have TCP/IP connectivity to (most of) the > > > ships, and AFAIK apt-get does not yet work over advanced > > > UUCP/minicom/kermit or other equivalent hich-tech dial up connection. > > > just joking :) > > >=20 > > >> On Fri, Jun 15, 2012 at 2:24 AM, Achilleas Mantzios > > >>=20 > > >> wrote: > > >> > On =CE=A0=CE=B1=CF=81 15 =CE=99=CE=BF=CF=85=CE=BD 2012 10:28:20 Sc= ott Marlowe wrote: > > >> >> You do realize you're missing four years of bug fixes right? > > >> >=20 > > >> > On =CE=A0=CE=B5=CE=BC 14 =CE=99=CE=BF=CF=85=CE=BD 2012 11:39:35 Ac= hilleas Mantzios 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. > > >> >=20 > > >> > 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 scenario minimum 21K USD for the whole fleet + > > >> > suspension of all other activities for two months. If physical > > >> > travel was involved, the cost would be increased at even higher > > >> > levels. > > >> >=20 > > >> >=20 > > >> > - > > >> > Achilleas Mantzios > > >> > IT DEPT > > >=20 > > > - > > > Achilleas Mantzios > > > IT DEPT > > >=20 > > > -- > > > Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) > > > To make changes to your subscription: > > > http://www.postgresql.org/mailpref/pgsql-sql >=20 > - > Achilleas Mantzios > IT DEPT =2D Achilleas Mantzios IT DEPT