Re: automatic analyze: readahead - add "IO read time" log message

From: Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: automatic analyze: readahead - add "IO read time" log message
Date: 2021-05-25 16:00:46
Message-ID: 9beada99-34ce-8c95-fadb-451768d08c64@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 11.02.2021 01:10, Stephen Frost wrote:

> Greetings,
>
> * Heikki Linnakangas (hlinnaka(at)iki(dot)fi) wrote:
>> On 05/02/2021 23:22, Stephen Frost wrote:
>>> Unless there's anything else on this, I'll commit these sometime next
>>> week.
>> One more thing: Instead of using 'effective_io_concurrency' GUC directly,
>> should call get_tablespace_maintenance_io_concurrency().
> Ah, yeah, of course.
>
> Updated patch attached.

I happened to notice that get_tablespace_io_concurrency() is called
instead of get_tablespace_maintenance_io_concurrency(). It doesn't look
right, no?

Regards,
Egor Rogov.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-05-25 16:09:18 Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c)
Previous Message Robert Haas 2021-05-25 15:46:05 Re: Race condition in recovery?