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

Re: Asynchronous I/O in Postgres

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: mladen(dot)gogala(at)vmsinfo(dot)com, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Asynchronous I/O in Postgres
Date: 2010-10-21 02:30:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docspgsql-novice
Josh Kupershmidt wrote:
> On Fri, Oct 8, 2010 at 8:14 AM, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> wrote:
> > Mladen Gogala wrote:
> >>
> >> So, essentially, the process is reading block by block, in a sequence.
> >> What, exactly, does "effective_io_concurrency" mean?
> >>
> >
> > To rephrase my question, can anybody tell me where in the code is it used?
> The docs are a bit sparse here :-(
> 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?

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + It's impossible for everything to be true. +

In response to


pgsql-novice by date

Next:From: Tom LaneDate: 2010-10-21 02:36:11
Subject: Re: "duplicate key value": version 8.4 vs 8.1
Previous:From: Turner, John JDate: 2010-10-21 02:04:17
Subject: source make check regression test on windows xp

pgsql-docs by date

Next:From: Bruce MomjianDate: 2010-10-21 21:29:11
Subject: Re: Gripe: bytea_output default => data corruption
Previous:From: Tom LaneDate: 2010-10-20 21:07:29
Subject: Re: Inaccurate comment for information_schema.triggered_update_columns

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