Message-Id: <4CEA49C80200002500037CF4@gw.wicourts.gov>
Date: Mon, 22 Nov 2010 10:45:28 -0600
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Achilleas Mantzios" <achill@matrix.gatewaynet.com>,
	<pgsql-admin@postgresql.org>
Subject: Re: FK disappeared in 8.3.3
References: <201011221213.32035.achill@matrix.gatewaynet.com>
	<4CEA30A90200002500037CE1@gw.wicourts.gov>
	<201011221757.18325.achill@matrix.gatewaynet.com>
In-Reply-To: <201011221757.18325.achill@matrix.gatewaynet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Achilleas Mantzios <achill@matrix.gatewaynet.com> wrote:
 
> (imagine having to upgrade 61 installations for which you dont
> have ssh/scp ;) sounds fun right? )
 
I don't have to imagine -- been there, done that.  (Not with ships
but large geographical distances and needing to trudge through
secure facilities with big steel doors every so many feet.)  It can
be time-consuming and tedious.  But then, so can recovering a
corrupted database.
 
If I were in your shoes, I'd consider arranging to have a CD-ROM
mailed to someone on each ship at its next port, with a script which
would automatically perform the update.  (Heavily tested in advance,
of course.)  I strongly recommend that you read through the release
notes of 8.3.4 to 8.3.12 and consider whether any of the fixes
incorporated in those releases, or the aggregate of all of them,
might be worth the effort involved in testing such a script and
burning such a CD-ROM.
 
Of course, none of that helps with your current issue; I would just
hate to see you pop up here in a few months with bigger problems
than this if it can be avoided.
 
-Kevin