Re: Insane behaviour in 8.3.3 - Mailing list pgsql-sql
From | Achilleas Mantzios |
---|---|
Subject | Re: Insane behaviour in 8.3.3 |
Date | |
Msg-id | 201206191217.49743.achill@matrix.gatewaynet.com Whole thread Raw |
In response to | Re: Insane behaviour in 8.3.3 (Achilleas Mantzios <achill@matrix.gatewaynet.com>) |
Responses |
Re: Insane behaviour in 8.3.3
|
List | pgsql-sql |
We had another corruption incident on the very same machine, this time in the 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 Δευ 18 Ιουν 2012 11:36:14 you wrote: > Thanx, well said, and especially after this incident we should very well > consider seriously an upgrade. > > On Παρ 15 Ιουν 2012 19:59:05 Scott Marlowe wrote: > > Well, I'd see about finding a way to upgrade to 8.3.19. 8.3.3 has > > know data eating bugs. > > > > On Fri, Jun 15, 2012 at 9:32 AM, Achilleas Mantzios > > > > <achill@matrix.gatewaynet.com> wrote: > > > On Παρ 15 Ιουν 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: > > >> > > >> sudo apt-get upgrade > > >> > > >> or similar and sit back and watch. > > > > > > 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 :) > > > > > >> On Fri, Jun 15, 2012 at 2:24 AM, Achilleas Mantzios > > >> > > >> <achill@matrix.gatewaynet.com> wrote: > > >> > 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 > > > > > > - > > > Achilleas Mantzios > > > IT DEPT > > > > > > -- > > > Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) > > > To make changes to your subscription: > > > http://www.postgresql.org/mailpref/pgsql-sql > > - > Achilleas Mantzios > IT DEPT - Achilleas Mantzios IT DEPT