* Robert Haas (robertmhaas@gmail.com) wrote:
> On Mon, Aug 10, 2015 at 3:23 AM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> > I've marked this as rejected in the commitfest, because others are
> > working on a more general solution with parallel workers. That's still
> > work-in-progress, and it's not certain if it's going to make it into
> > 9.6, but if it does it will largely render this obsolete. We can revisit
> > this patch later in the release cycle, if the parallel scan patch hasn't
> > solved the same use case by then.
>
> I think the really important issue for this patch is the one discussed here:
>
> http://www.postgresql.org/message-id/CA+TgmoaiJK1svzw_GkFU+zsSxciJKFELqu2AOMVUPhpSFw4BsQ@mail.gmail.com
I agree that it'd be great to figure out the answer to #2, but I'm also
of the opinion that we can either let the user tell us through the use
of the GUCs proposed in the patch or simply not worry about the
potential for time wastage associated with starting them all at once, as
you suggested there.
> You raised an important issue there but never really expressed an
> opinion on the points I raised, here or on the other thread. And
> neither did anyone else except the patch author who, perhaps
> unsurprisingly, thinks it's OK. I wish we could get more discussion
> about that.
When I read the proposal, I had the same reaction that it didn't seem
like quite the right place and it further bothered me that it was
specific to FDWs.
Perhaps not surprisingly, as I authored it, but I'm still a fan of my
proposal #1 here:
http://www.postgresql.org/message-id/20131104032604.GB2706@tamriel.snowman.net
More generally, I completely agree with the position (I believe your's,
but I might be misremembering) that we want to have this async
capability independently and in addition to parallel scan. I don't
believe one obviates the advantages of the other.
Thanks!
Stephen
