From: David Boreham <david_list@boreham.org>
To: pgsql-hackers@postgresql.org
Subject: Re: ice-broker scan thread
Date: Tue, 29 Nov 2005 08:01:30 -0700
Message-ID: <438C6D4A.4000103@boreham.org> (raw)
In-Reply-To: <6418CC03D0FB1943A464E1FEFB3ED46B01B220E7@im01.cincom.com>
References: <6418CC03D0FB1943A464E1FEFB3ED46B01B220E7@im01.cincom.com>
>threw up some threads to read ahead, then my user thread and my read
>ahead threads would thrash on trying to lock the buffer slots. So, I
>had the read ahead threads start at some distance into the table, and
>work toward the beginning. The user thread would do its own I/O until
>
>
Ah. The lightbulb went on. You want multiple outstanding I/O operations
in the case that table or index spans multiple physical disks.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: david_list@boreham.org
Subject: Re: ice-broker scan thread
In-Reply-To: <438C6D4A.4000103@boreham.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox