Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-www-owner+archive@lists.postgresql.org>)
	id 1hKrVP-00011G-UG
	for pgsql-www@arkaria.postgresql.org; Sun, 28 Apr 2019 21:38:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-www-owner+archive@lists.postgresql.org>)
	id 1hKrVO-0006AF-Ky
	for pgsql-www@arkaria.postgresql.org; Sun, 28 Apr 2019 21:38:38 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <ishii@sraoss.co.jp>)
	id 1hKrVO-0006A8-EA
	for pgsql-www@lists.postgresql.org; Sun, 28 Apr 2019 21:38:38 +0000
Received: from sraihb2.sra.co.jp ([202.32.10.6])
	by magus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <ishii@sraoss.co.jp>)
	id 1hKrVK-0002x4-7l
	for pgsql-www@lists.postgresql.org; Sun, 28 Apr 2019 21:38:37 +0000
Received: from srascf.sra.co.jp (srascf [133.137.8.80])
	by sraihb2.sra.co.jp (Postfix) with ESMTP id ED1A12A15EC
	for <pgsql-www@lists.postgresql.org>; Mon, 29 Apr 2019 06:38:30 +0900 (JST)
Received: from srascb.sra.co.jp (unknown [133.137.8.65]) by srascf.sra.co.jp
 with smtp
	 id 139a_0027_0624363e_1407_433a_8c69_c42175a929e9;
	Mon, 29 Apr 2019 06:38:30 +0900
Received: from sranhm.sra.co.jp (osspc25 [133.137.174.97])
	by srascb.sra.co.jp (Postfix) with ESMTP id 9F9E72D6943
	for <pgsql-www@lists.postgresql.org>; Mon, 29 Apr 2019 06:38:30 +0900 (JST)
Received: from localhost (sraihb-hub.sra.co.jp [133.137.8.6])
	by sranhm.sra.co.jp (Postfix) with ESMTP id 59B20A0A56;
	Mon, 29 Apr 2019 06:38:30 +0900 (JST)
Date: Mon, 29 Apr 2019 06:38:30 +0900 (JST)
Message-Id: <20190429.063830.371372237913446079.t-ishii@sraoss.co.jp>
To: jkatz@postgresql.org
Cc: daniel@yesql.se, magnus@hagander.net, euler@timbira.com.br,
 pgsql-www@lists.postgresql.org, jtara-github@spamex.com
Subject: Re: BUG #15706: Support Services page out of date,Re: BUG #15706:
 Support Services page out of date
From: Tatsuo Ishii <ishii@sraoss.co.jp>
In-Reply-To: <ff64dabb-f544-ac49-e442-c835fdba5bbb@postgresql.org>
References: 
 <nnaVBg86IghiaxiYkCAU9XA9VklOeBuv05GyUGUJloHu0QwGsDCNIzVh8kauw_XTRx6hpJ3IR6SIOWPIc80QBbTQr9Y0VEof0b-I-f9JE58=@yesql.se>
	<847625e0-7726-0cf7-8c68-ec2500a07b45@postgresql.org>
	<ff64dabb-f544-ac49-e442-c835fdba5bbb@postgresql.org>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
List-Id: <pgsql-www.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-www@lists.postgresql.org>
List-Owner: <mailto:pgsql-www-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-www>
Precedence: bulk

> 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@hagander=
.net>
>>> wrote:
>>>> On Thu, Mar 21, 2019 at 1:20 AM Jonathan S. Katz <jkatz@postgresql=
.org
>>>> <mailto:jkatz@postgresql.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 buil=
ding
>>>> it. There was even a db field for it in the early dev snapshots, b=
ut
>>>> it was removed since it was never quite done.
>>>>
>>>> The general idea was to just have a "last confirmed" timestamp fie=
ld
>>>> on each entry, and just stop showing any entries that have not bee=
n
>>>> confirmed in <n> days/weeks/months/whatever. We can keep them arou=
nd
>>>> some extra time beyond that in case people come back to update the=
m
>>>> later of course.
>>>
>>> I think it makes sense to remove after a set timeout, if the user h=
asn'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=A0+1 for doing the same for products.=A0
> =

> 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 / we=
nt
> to things I wish I could unsee.
> =

> I would say this was more stale than I thought too, but given that th=
ere
> has not been a product scrub as long as I can remember, it's not as b=
ad
> as the staleness of the services.
> =

> Regardless, let's work on getting that system into place to help mana=
ge
> 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