| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Robins Tharakan <tharakan(at)gmail(dot)com>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | Re: Planet PostgreSQL Bug |
| Date: | 2016-03-29 09:25:28 |
| Message-ID: | CAM3SWZTtBsgEGvErm4+kNP=pHf=9vrcnh8xo8pHW50avjf+tYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Tue, Mar 29, 2016 at 1:42 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Hi,
>>
>> Not sure if many have noticed, but seems like the Planet.PostgreSQL.org
>> Feed parser accepts a foreign post's date / time at face value and thus, if
>> things be this way, we're going to see Alexander Korotkov's empty post for
>> the next few months (till 26th August 2016, to be precise).
>
>
> Oops.
>
> I've edited the in-place post and set it to march instead of august. That
> should bump it down the list at the next update.
>
> I've also CCed Alexander on this - Alexander, clearly your blog software is
> broken wrt date handling.
>
>
>>
>> Probably the feed parser, should cap the post date to (at max) be current
>> date, or something like that.
>
>
> Yeah, that's a good idea. Will do.
>
> Thanks for noticing and pointing it out!
I've CC'd him here. You seem to have missed him.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-03-29 09:33:06 | Re: Planet PostgreSQL Bug |
| Previous Message | Magnus Hagander | 2016-03-29 08:42:13 | Re: Planet PostgreSQL Bug |