pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Insane behaviour in 8.3.3
Date: Fri, 15 Jun 2012 11:24:44 +0300
Message-ID: <201206151124.45021.achill@matrix.gatewaynet.com> (raw)
In-Reply-To: <CAOR=d=1Tp1X6qyPXHZjEeWJ2D-TVST3fgxL3R4DYmiS0Am9d6A@mail.gmail.com>
References: <201206141139.35601.achill@matrix.gatewaynet.com>
	<201206151025.32973.achill@matrix.gatewaynet.com>
	<CAOR=d=1Tp1X6qyPXHZjEeWJ2D-TVST3fgxL3R4DYmiS0Am9d6A@mail.gmail.com>

On Παρ 15 Ιουν 2012 10:28:20 Scott Marlowe wrote:
> You do realize you're missing four years of bug fixes right?

On Πεμ 14 Ιουν 2012 11:39:35 Achilleas 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.
> 
> 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 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.


-
Achilleas Mantzios
IT DEPT



view thread (24+ messages)  latest in thread

Message-ID: <201206151124.45021.achill@matrix.gatewaynet.com>
Permalink:  ../201206151124.45021.achill@matrix.gatewaynet.com/
Also on:    postgresql.org/message-id/201206151124.45021.achill@matrix.gatewaynet.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: achill@matrix.gatewaynet.com, scott.marlowe@gmail.com
  Subject: Re: Insane behaviour in 8.3.3
  In-Reply-To: <201206151124.45021.achill@matrix.gatewaynet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox