Re: [HACKERS] logical replication launcher crash on buildfarm - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] logical replication launcher crash on buildfarm
Date
Msg-id CA+TgmoZRtrxLuGMQNrPqpn6ks9EFURp1mWcf3d8qDQFpOBwdsQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] logical replication launcher crash on buildfarm  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Apr 15, 2017 at 12:01 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Maybe we need to rethink the division of labor between parallel.c
> and execParallel.c, but that would depend on somebody explaining
> what the difference is in the first place.

parallel.c handles general concerns related to any sort of
parallelism, particularly those related to transaction management,
hence it's in src/backend/access/transam. execParallel.c handles
concerns that are specific to the executor, hence it's in
src/backend/executor.  The header comment for execParallel.c is fairly
informative on this point; now that I look at it, parallel.c has only
a stub comment, which really ought to be expanded.  Note that while
parallel *query* uses both, a parallel utility command will likely use
only the facilities in parallel.c, so the distinction is not academic.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: [HACKERS] Re: extended stats not friendly towards ANALYZE withsubset of columns
Next
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] SCRAM authentication, take three