Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id D9A65633508
	for <pgsql-www-postgresql.org@mail.postgresql.org>;
	Tue, 12 May 2009 02:48:22 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 98299-02 for
	<pgsql-www-postgresql.org@mail.postgresql.org>;
	Tue, 12 May 2009 02:48:21 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by mail.postgresql.org (Postfix) with ESMTP id 3EF11633386
	for <pgsql-www@postgresql.org>; Tue, 12 May 2009 02:48:21 -0300 (ADT)
Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and
	authenticated) by svr2.hagander.net (Postfix) with ESMTP id
	7FD25DCD326; Tue, 12 May 2009 07:48:19 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by mha-laptop.hagander.net (Postfix) with ESMTP id BADF8124127;
	Tue, 12 May 2009 07:48:18 +0200 (CEST)
Message-ID: <4A090DA2.3050004@hagander.net>
Date: Tue, 12 May 2009 07:48:18 +0200
From: Magnus Hagander <magnus@hagander.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: Josh Berkus <josh@agliodbs.com>
CC: PostgreSQL www <pgsql-www@postgresql.org>
Subject: Re: Problem with Josh Tolley blog feed
References: <4A08C2C6.30702@agliodbs.com> <4A08C31F.5050908@agliodbs.com>
In-Reply-To: <4A08C31F.5050908@agliodbs.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200905/49
X-Sequence-Number: 17030

Josh Berkus wrote:
> On 5/11/09 5:28 PM, Josh Berkus wrote:
>> All,
>>
>> Somehow Josh's RSS feed also includes every planetpostgres post for the
>> last 2 months, at least as far as planet is concerned. Fix?
>>
> 
> Oops!  Wrong Planet.  Will bug Devrim.

Also, this is not actually Josh's blog - it's the endpoint shared blog
that happens to come out has him.

I have no idea why this happened thouhg - planet.postgresql.org didn't
see any issues with their feed, and they both use the same feed parsing
library.. Must be something it stores differently, but I don't think
there was ever anything wrong with the feed itself.

//Magnus