On 23.04.25 11:14, Daniel Gustafsson wrote:
On 23 Apr 2025, at 09:16, Laurenz Albe wrote:
On Wed, 2025-04-23 at 00:21 -0500, Igor Korot wrote:
However, this page
https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY
describes both default and mn/max
On Wednesday, April 23, 2025, Igor Korot wrote:
>
> The question is more about the default value...
>
0 or 1, determined at server compilation time. You quoted the
documentation that says this…
David J.
Hi, David,
On Thu, Apr 24, 2025 at 12:23 AM David G. Johnston
wrote:
>
> On Wednesday, April 23, 2025, Igor Korot wrote:
>>
>>
>> How do you handle sch situation from the client POV?
>
>
> Get the current value. If it’s non-zero the system definitely supports it.
> If it’s zero it probably do
Hi, Laurenz,
On Wed, Apr 23, 2025 at 2:16 AM Laurenz Albe wrote:
>
> On Wed, 2025-04-23 at 00:21 -0500, Igor Korot wrote:
> > On the page
> > https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-SEQ-PAGE-COST
> >
> > it is only given the default value of this parameter.
> >
> >
On Wednesday, April 23, 2025, Igor Korot wrote:
>
> How do you handle sch situation from the client POV?
>
Get the current value. If it’s non-zero the system definitely supports
it. If it’s zero it probably doesn’t. But give the user an option to
specify a value anyway just in case. If they
Tom,
On Wed, Apr 23, 2025 at 1:40 PM Tom Lane wrote:
>
> 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
Tom,
On Wed, Apr 23, 2025 at 1:40 PM Tom Lane wrote:
> 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
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 "d
Hi, Tom,
On Wed, Apr 23, 2025 at 1:28 PM Tom Lane wrote:
> Daniel Gustafsson writes:
> >> On 23 Apr 2025, at 09:16, Laurenz Albe
> 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
Daniel Gustafsson writes:
>> On 23 Apr 2025, at 09:16, Laurenz Albe 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,
>> b
On Tuesday, April 22, 2025, Igor Korot wrote:
> Hi, ALL,
>
> On the page https://www.postgresql.org/docs/current/runtime-config-
> query.html#GUC-SEQ-PAGE-COST
>
> it is only given the default value of this parameter.
>
> No min/max values are provided..
>
> The same can be sad about
> https://ww
> On 23 Apr 2025, at 09:16, Laurenz Albe wrote:
> On Wed, 2025-04-23 at 00:21 -0500, Igor Korot wrote:
>> However, this page
>> https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY
>> describes both default and mn/max, however t s says:
>>
>> [quote]
On Wed, 2025-04-23 at 00:21 -0500, Igor Korot wrote:
> On the page
> https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-SEQ-PAGE-COST
>
> it is only given the default value of this parameter.
>
> No min/max values are provided..
>
> The same can be sad about
> https://www.pos
13 matches
Mail list logo
