From: Mark Lewis <mark.lewis@mir3.com>
To: Bucky Jordan <bjordan@lumeta.com>
Cc: Luke Lonergan <llonergan@greenplum.com>
Cc: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Large tables (was: RAID 0 not as fast as
Date: Thu, 21 Sep 2006 12:41:54 -0700
Message-ID: <1158867714.9657.1680.camel@archimedes> (raw)
In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4209A6E@MAIL.corp.lumeta.com>
References: <78ED28FACE63744386D68D8A9D1CF5D4209A6E@MAIL.corp.lumeta.com>
> So this might be a dumb question, but the above statements apply to the
> cluster (e.g. postmaster) as a whole, not per postgres
> process/transaction correct? So each transaction is blocked waiting for
> the main postmaster to retrieve the data in the order it was requested
> (i.e. not multiple scanners/aio)?
Each connection runs its own separate back-end process, so these
statements apply per PG connection (=process).
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-performance@postgresql.org
Cc: mark.lewis@mir3.com, bjordan@lumeta.com, llonergan@greenplum.com, schabi@logix-tt.com
Subject: Re: Large tables (was: RAID 0 not as fast as
In-Reply-To: <1158867714.9657.1680.camel@archimedes>
* 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