Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u7f1p-003SP4-1z for pgsql-general@arkaria.postgresql.org; Wed, 23 Apr 2025 18:41:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u7f1m-008vgp-EA for pgsql-general@arkaria.postgresql.org; Wed, 23 Apr 2025 18:40:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u7f1m-008vgh-2r for pgsql-general@lists.postgresql.org; Wed, 23 Apr 2025 18:40:58 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u7f1k-001ZzX-1V for pgsql-general@lists.postgresql.org; Wed, 23 Apr 2025 18:40:57 +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 53NIesqq1431983; Wed, 23 Apr 2025 14:40:54 -0400 From: Tom Lane To: Igor Korot cc: Daniel Gustafsson , Laurenz Albe , "pgsql-generallists.postgresql.org" Subject: Re: Another documentation issue In-reply-to: References: <03763b6b43cfd8a7194c2fb06452178db4256494.camel@cybertec.at> <4B9E0CAC-FB06-4F35-8C77-33AEA7F741B7@yesql.se> <1430373.1745432896@sss.pgh.pa.us> Comments: In-reply-to Igor Korot message dated "Wed, 23 Apr 2025 13:32:50 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1431981.1745433654.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 23 Apr 2025 14:40:54 -0400 Message-ID: <1431982.1745433654@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Igor Korot writes: > On Wed, Apr 23, 2025 at 1:28 PM Tom Lane wrote: >> If we do anything about this, I'd just say "systems that have >> posix_fadvise()". If we write something more specific it's likely to >> become obsolete, and it doesn't seem to me that it's hard for someone >> to research "does my box have posix_fadvise()? > Imagine a person that wants to write a program which will cover creating > the table space. > Such person needs to cover the appropriate fields with possible values. > Is there a #define such person should check to cover the appropriate values? HAVE_POSIX_FADVISE. Seems to me it'd be way easier to find that from documentation that mentions posix_fadvise than from documentation that says "it works on systems X, Y, Z". regards, tom lane