From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | "Myron Scott" <lister(at)sacadia(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Support Parallel Query Execution in Executor |
Date: | 2006-04-09 18:39:41 |
Message-ID: | 12625.1144607981@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> On 4/9/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I was considering a variant idea in the shower this morning:suppose
>> that we invent one or more "background reader" processes that have
>> basically the same infrastructure as the background writer, but have
>> the responsibility of causing buffer reads to happen at useful times
> This is sort of what I'm playing with. There are N-number of backends
> which are configured at startup and are available solely for parallel
> processing.
That's not remotely the same thing: a backend is a very different animal
from a bgwriter. In particular, bgwriter (and bgreaders if we had 'em)
aren't database-specific, don't need to think about permission checking
as they don't execute on behalf of particular users, don't have syscaches
to keep in-sync with everything else, etc etc.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-09 18:48:54 | Re: Support Parallel Query Execution in Executor |
Previous Message | Gregory Maxwell | 2006-04-09 18:18:04 | Re: Support Parallel Query Execution in Executor |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-09 18:48:54 | Re: Support Parallel Query Execution in Executor |
Previous Message | Alvaro Herrera | 2006-04-09 18:33:13 | Re: [WIP] Add relminxid column to pg_class |