Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pkVqn-0003tq-4E for pgsql-www@arkaria.postgresql.org; Thu, 06 Apr 2023 20:04:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pkVql-0003CG-Sv for pgsql-www@arkaria.postgresql.org; Thu, 06 Apr 2023 20:04:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pkVql-0003C7-La for pgsql-www@lists.postgresql.org; Thu, 06 Apr 2023 20:04:51 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pkVqf-0004Js-5z for pgsql-www@lists.postgresql.org; Thu, 06 Apr 2023 20:04:50 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 336K4hR82659090; Thu, 6 Apr 2023 16:04:43 -0400 From: Tom Lane To: Imre Samu cc: pgsql-www@lists.postgresql.org Subject: Re: PostgreSQL Mailing list public archives : search not working ... In-reply-to: References: Comments: In-reply-to Imre Samu message dated "Thu, 06 Apr 2023 19:45:59 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2659088.1680811483.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 06 Apr 2023 16:04:43 -0400 Message-ID: <2659089.1680811483@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk [ redirecting to -www list ] Imre Samu writes: > My use case: > in https://www.postgresql.org/list/ -> "Search the Archives" > search for the "large database backup" > -> > https://www.postgresql.org/search/?m=3D1&q=3Dlarge+database+backup&l=3D&= d=3D365&s=3Dr > -> "Your search for large database backup returned no hits." > But at least one big thread exists: > To: pgsql-general > Subject: postgres *large database backup* > Date: 2022-11-30 15:40:23 > https://www.postgresql.org/message-id/flat/CA%2BONtZ7CdiJ2X8x_8sPHR%2Btz= -vv7mR1uoDzLia3fzWVZA9k0JQ%40mail.gmail.com > *Changing the "Sort by" ..* > - sort by: rank: no hits > https://www.postgresql.org/search/?m=3D1&q=3Dlarge+database+backup&l=3D&= d=3D365&s=3Dr > - sort by: date: OK ; 1 result > https://www.postgresql.org/search/?m=3D1&q=3Dlarge+database+backup&l=3D&= d=3D365&s=3Dd > - sort by: reverse date : no hits. > https://www.postgresql.org/search/?m=3D1&q=3Dlarge+database+backup&l=3D&= d=3D365&s=3Di I can confirm that this example gives different result sets depending on the choice of sort order. Surely that's a bug? I have little idea what's going on under the hood though. regards, tom lane