| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Igor Korot <ikorot01(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Another documentation issue |
| Date: | 2025-04-23 18:40:54 |
| Message-ID: | 1431982.1745433654@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Igor Korot <ikorot01(at)gmail(dot)com> writes:
> On Wed, Apr 23, 2025 at 1:28 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pawel Veselov | 2025-04-23 18:46:39 | Dump version issues |
| Previous Message | Igor Korot | 2025-04-23 18:32:50 | Re: Another documentation issue |