Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 616A8CE6EC for ; Fri, 15 Jun 2012 07:01:38 -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 1SfTLU-0007GD-Er for pgsql-sql@postgresql.org; Fri, 15 Jun 2012 10:01:37 +0000 Received: from smadev.internal.net (localhost [127.0.0.1]) by smadev.internal.net (8.14.5/8.14.5) with ESMTP id q5FA1JIr034209 for ; Fri, 15 Jun 2012 13:01:19 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) Received: (from achill@localhost) by smadev.internal.net (8.14.5/8.14.5/Submit) id q5FA1JpU034208 for pgsql-sql@postgresql.org; Fri, 15 Jun 2012 13:01:19 +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: Fri, 15 Jun 2012 13:01:19 +0300 User-Agent: KMail/1.13.7 (FreeBSD/8.3-RELEASE; KDE/4.7.3; amd64; ; ) References: <201206141139.35601.achill@matrix.gatewaynet.com> <201206151124.45021.achill@matrix.gatewaynet.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201206151301.19550.achill@matrix.gatewaynet.com> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201206/43 X-Sequence-Number: 36697 On =CE=A0=CE=B1=CF=81 15 =CE=99=CE=BF=CF=85=CE=BD 2012 12:28:21 Samuel Gend= ler wrote: > On Fri, Jun 15, 2012 at 1:24 AM, Achilleas Mantzios < >=20 > achill@matrix.gatewaynet.com> wrote: > > 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 > And what is the cost of data corruption on large numbers of systems? And > how much to fix that, especially if multiple systems fail at the same tim= e? > Some things aren't free. $21K in exchange for NOT having had to keep > systems up to date for 4 years seems like a decent trade. After 12 years of using PostgreSQL in this environment, I can assure you th= at things are not so scary. We have multiple plans of action in case a slave installation totally gets = damaged,=20 plus PostgreSQL has been a real beast of reliability. Also here you neglet the cost of actual migration, test plans, which adds t= o the whole picture. Moving from 7.4 to 8.3 back in 2008, was not easy at all (tsearch, intarray= , loads of black magic, etc..).=20 You could no just send a tech guy to the ship to perform the migration, he = would have to know what he is actually doing and why when executing the 100 lines script line = by line. Some time in the future, we will commence another round of migration,=20 (at any point in time we need to support all current working versions) =20 but we will have to feel a substantial reason to do so. =2D Achilleas Mantzios IT DEPT