Re: Another documentation issue
От | Igor Korot |
---|---|
Тема | Re: Another documentation issue |
Дата | |
Msg-id | CA+FnnTz5tbFf_sHmfkGQZTquxDDgdfq5UVmh0gCSQGPbtoT0vw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Another documentation issue (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Another documentation issue
|
Список | pgsql-general |
Hi, Tom,
On Wed, Apr 23, 2025 at 1:28 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Daniel Gustafsson <daniel@yesql.se> writes:
>> On 23 Apr 2025, at 09:16, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>> On Wed, 2025-04-23 at 00:21 -0500, Igor Korot wrote:
>>> No explanation of what is "supported system" is given...
>> According to the source, it is "systems that have posix_fadvise()". We could document that,
>> but I don't know if it would help many people. I am not sure how easy and feasible it is
>> to research which versions of which operating systems qualify.
>> From memory it's supported on FreeBSD, NetBSD and Linux with Windows, macOS and
> OpenBSD not supporting it. Assuming I'm not completely wrong (a 1 minute
> search shows it's in the ballpark) we could perhaps add something like
> "Unsupported platforms include (but isn't limited to) Windows and macOS" which
> would provide a bit more clarity.
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?
Thank you?
".
regards, tom lane
В списке pgsql-general по дате отправления: