Re: BUG #15706: Support Services page out of date,Re: BUG #15706: Support Services page out of date

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: jkatz(at)postgresql(dot)org
Cc: daniel(at)yesql(dot)se, magnus(at)hagander(dot)net, euler(at)timbira(dot)com(dot)br, pgsql-www(at)lists(dot)postgresql(dot)org, jtara-github(at)spamex(dot)com
Subject: Re: BUG #15706: Support Services page out of date,Re: BUG #15706: Support Services page out of date
Date: 2019-04-28 21:38:30
Message-ID: 20190429.063830.371372237913446079.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-www

> On 4/26/19 11:48 PM, Jonathan S. Katz wrote:
>> On 3/25/19 5:33 AM, Daniel Gustafsson wrote:
>>> On Sunday, March 24, 2019 6:50 PM, Magnus Hagander <magnus(at)hagander(dot)net>
>>> wrote:
>>>> On Thu, Mar 21, 2019 at 1:20 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org
>>>> <mailto:jkatz(at)postgresql(dot)org>> wrote:
>>>>
>>>> Some of the pgweb folks have discussed doing that before; it's not
>>>> a bad
>>>> idea, and perhaps would cut down on some of the headaches.
>>>>
>>>>
>>>> That was in fact the original plan, nobody just got around to building
>>>> it. There was even a db field for it in the early dev snapshots, but
>>>> it was removed since it was never quite done.
>>>>
>>>> The general idea was to just have a "last confirmed" timestamp field
>>>> on each entry, and just stop showing any entries that have not been
>>>> confirmed in <n> days/weeks/months/whatever. We can keep them around
>>>> some extra time beyond that in case people come back to update them
>>>> later of course.
>>>
>>> I think it makes sense to remove after a set timeout, if the user hasn't
>>> verified in 3 months (or some
>>> other sufficiently long period) then the odds that the entry is out of
>>> date seems quite high.
>>>
>>>> Oh, and +1 for doing the same for products. 
>
> OK, so I did the scrub for products.
>
>> The scrub took me about 2 hours and change.
>
> Fortunately, products are a bit more straightforward and did not take as
> long as services, though it was still at least an hour. So whatever
> system we put in place for services, I suggest the same for products
>
> There were 210 products listed at the beginning of the scrub.
>
> - 170 remain
> - 40 were removed as they did not exist + no obvious replacement / went
> to things I wish I could unsee.
>
> I would say this was more stale than I thought too, but given that there
> has not been a product scrub as long as I can remember, it's not as bad
> as the staleness of the services.
>
> Regardless, let's work on getting that system into place to help manage
> it so scrubs are less gargantuan tasks.

Are we working on this region only?
https://www.postgresql.org/support/professional_support/northamerica/

Some of the companies listed in the northamerica page also appear in
other regions (I only checked aisa though). I think companies removed
from the northamerica region should also be removed from other regions
as well unless they explicitly stat that they have different entities
in the other regions.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jonathan S. Katz 2019-04-28 21:41:30 Re: BUG #15706: Support Services page out of date,Re: BUG #15706: Support Services page out of date
Previous Message Damir Ciganović-Janković 2019-04-28 17:32:48 Re: BUG #15779: Partition elimination doesn't work as expected when using PARTITION BY RANGE

Browse pgsql-www by date

  From Date Subject
Next Message Jonathan S. Katz 2019-04-28 21:41:30 Re: BUG #15706: Support Services page out of date,Re: BUG #15706: Support Services page out of date
Previous Message Jonathan S. Katz 2019-04-28 01:37:53 Re: BUG #15706: Support Services page out of date