Re: postgres_fdw vs. force_parallel_mode on ppc - Mailing list pgsql-hackers

From Robert Haas
Subject Re: postgres_fdw vs. force_parallel_mode on ppc
Date
Msg-id CA+TgmoaDq4aqPT_ECWMK9ZZj6ErPWLwDH-4OCLOcsjYNu5p2iA@mail.gmail.com
Whole thread Raw
In response to Re: postgres_fdw vs. force_parallel_mode on ppc  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: postgres_fdw vs. force_parallel_mode on ppc
List pgsql-hackers
On Wed, Feb 24, 2016 at 12:59 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Wed, Feb 24, 2016 at 5:48 PM, Thomas Munro
> <thomas.munro@enterprisedb.com> wrote:
>> Here is a first pass at that. [...]
>
> On Wed, Feb 24, 2016 at 1:23 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> file_fdw is parallel-safe, ...
>
> And here is a patch to apply on top of the last one, to make file_fdw
> return true.  But does it really work correctly under parallelism?

Seems like it.  Running the regression tests for file_fdw under
force_parallel_mode=regress, max_parallel_degree>0 passes; you can
verify that's actually doing something by using
force_parallel_mode=on, which will result in some predictable
failures.  From a theoretical point of view, there's no reason I can
see why reading a file shouldn't work just as well from a parallel
worker as from the leader.  They both have the same view of the
filesystem, and in neither case are we trying to write any data; we're
just trying to read it.

Committed these patches after revising the comment you wrote and
adding documentation.

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



pgsql-hackers by date:

Previous
From: Pavel Raiskup
Date:
Subject: Re: pg_filedump patch for 9.5
Next
From: Robert Haas
Date:
Subject: Re: get current log file