Skip site navigation (1) Skip section navigation (2)

Re: [NOVICE] Asynchronous I/O in Postgres

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: mladen(dot)gogala(at)vmsinfo(dot)com, pgsql-docs(at)postgresql(dot)org
Subject: Re: [NOVICE] Asynchronous I/O in Postgres
Date: 2010-10-27 00:46:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docspgsql-novice
[moving to -docs]

On Wed, Oct 20, 2010 at 10:30 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Josh Kupershmidt wrote:
>> But it looks to me like effective_io_concurrency only affects bitmap
>> heap scans. The setting from effective_io_concurrency gets put into
>> "target_prefetch_pages" in ./src/backend/utils/misc/guc.c . But the
>> only place which uses that variable is
>> ./src/backend/executor/nodeBitmapHeapscan.c.
>> The EnterpriseDB docs
>> <>
>> mention:
>> "effective_io_concurrency is only used for Bitmap Heap Scans. For
>> normal sequential scans the operating system should handle read-ahead
>> internally (On Linux, see the blockdev command, in particular --setra
>> and --setfra)."
> So, this this also true for community Postgres?  Can someone suggest
> updated docs?

It looks like effective_io_concurrency only has an impact on bitmap
heap scans. I think a brief mention of this fact in the docs for
effective_io_concurrency should suffice, patch attached.


Attachment: effective_io_concurrency-doc.patch
Description: application/octet-stream (986 bytes)

In response to


pgsql-novice by date

Next:From: Robert HaasDate: 2010-10-27 01:46:44
Subject: Re: [NOVICE] Asynchronous I/O in Postgres
Previous:From: scorpdaddyDate: 2010-10-26 11:30:48
Subject: Re: [NOVICE] Need help with a query

pgsql-docs by date

Next:From: ljbDate: 2010-10-27 01:11:42
Subject: Re: [GENERAL] Gripe: bytea_output default => data corruption
Previous:From: Katharina kuhnDate: 2010-10-26 22:02:49

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group