Re: Support Parallel Query Execution in Executor

From: Markus Schiltknecht <markus(at)bluegap(dot)ch>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Support Parallel Query Execution in Executor
Date: 2006-04-10 18:26:14
Message-ID: 1144693574.4895.2.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Hi,

On Mon, 2006-04-10 at 13:36 -0400, Alvaro Herrera wrote:
> An idea arising in chat with Joshua Drake: the retargetting code, if it
> turns out to work and not be excessively expensive, could also be useful
> to implement a server-side "connection pooling" of sorts: the postmaster
> could keep idle backends and retarget them to a database that receives
> an incoming connection. However, we'd also need a mechanism to clean
> all backend state previous to reusing a connection, to leave it "as
> new" (no prepared statements, WITH HOLD cursors, etc.)

I suspect that's what I was calling 'pre-forking'. Please also note that
this would be the most difficult of my three examples (by difficulty of
implementation).

Regards

Markus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Luke Lonergan 2006-04-10 19:02:56 Re: Support Parallel Query Execution in Executor
Previous Message Alvaro Herrera 2006-04-10 17:36:45 Re: Support Parallel Query Execution in Executor

Browse pgsql-patches by date

  From Date Subject
Next Message Luke Lonergan 2006-04-10 19:02:56 Re: Support Parallel Query Execution in Executor
Previous Message Alvaro Herrera 2006-04-10 17:36:45 Re: Support Parallel Query Execution in Executor