X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 5B2025E4732
	for <pgsql-www-postgresql.org@localhost.postgresql.org>;
	Tue,  7 Sep 2004 14:08:44 +0100 (BST)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 88506-03
	for <pgsql-www-postgresql.org@localhost.postgresql.org>;
	Tue,  7 Sep 2004 13:08:42 +0000 (GMT)
Received: from mail.iinet.net.au (mail-07.iinet.net.au [203.59.3.39])
	by svr1.postgresql.org (Postfix) with SMTP id 415DC5E4724
	for <pgsql-www@postgresql.org>; Tue,  7 Sep 2004 14:08:37 +0100 (BST)
Received: (qmail 7578 invoked from network); 7 Sep 2004 13:08:15 -0000
Received: from unknown (HELO ?192.168.10.3?) (203.173.9.137)
	by mail.iinet.net.au with SMTP; 7 Sep 2004 13:08:15 -0000
Message-ID: <413DB2BD.1060202@postgresql.org>
Date: Tue, 07 Sep 2004 23:08:13 +1000
From: Justin Clift <justin@postgresql.org>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Chris Ryan <xgbe@yahoo.com>
Cc: pgsql-www@postgresql.org
Subject: Re: [Fwd: -1 Pgautotune-general moderator request(s)
References: <20040907125701.24864.qmail@web40004.mail.yahoo.com>
In-Reply-To: <20040907125701.24864.qmail@web40004.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200409/59
X-Sequence-Number: 5129

Chris Ryan wrote:
> Justin,
> 
>     I fixed the problem on that list. I have sent you a seperate email
> with a new password as well.

Thanks Chris.


 > Does anyone know if this problem is still
> occurring in places? I only know how to fix it on a per list basis so
> just let me know if you can't get into a list and I can help out.

No idea.

Might be worth asking on a Mailman users mailing list or something if 
there's a util that can analyse/scan/integrity-check for problem things 
like this.

Seems like a pretty nasty upgrade side-effect (if that's what caused it).

Regards and best wishes,

Justin Clift

> Chris Ryan