Message-ID: <415B7FCB.3010508@commandprompt.com>
Date: Wed, 29 Sep 2004 20:38:51 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL www <pgsql-www@postgresql.org>,
	PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [pgsql-advocacy] Server unreliability - Solutions 
References: <200409291713.i8THDLn14086@candle.pha.pa.us>
In-Reply-To: <200409291713.i8THDLn14086@candle.pha.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

>o  Archives
>
>The archives situation is a continual problem.  Again, maybe a dancing
>bear can help.  :-)
>  
>
This  is being resolved by Command Prompt. Marc and I are in the process 
of moving archives as we speak.
In fact DNS should be propagating by morning.

>Basically, with no money and no one offering servers, I don't see a good
>solution to any of these problems, but I think we need to recognize
>these are problems and that we will continue to suffer until they are
>addressed.  
>
>  
>
Command Prompt has offered servers and bandwidth on Multiple occassions. 
We have top notch
redundant bandwidth, natural gas fired generators, and solid uptime.

>Are there any proposals, no matter how radical, to correct these?
>
>  
>
Please see above.

Sincerely,

Joshua D. Drake


-- 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL