Re: Asynchronous Append on postgres_fdw nodes. - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Asynchronous Append on postgres_fdw nodes.
Date
Msg-id CAPmGK16taCSD56k1cu9HptYBdJBQnWS4OUNQKnEvq=s_9k_Ntg@mail.gmail.com
Whole thread Raw
In response to Re: Asynchronous Append on postgres_fdw nodes.  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Responses Re: Asynchronous Append on postgres_fdw nodes.  (Etsuro Fujita <etsuro.fujita@gmail.com>)
List pgsql-hackers
I'm resending this because I failed to reply to all.

On Sat, May 8, 2021 at 12:55 AM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> On Fri, May 7, 2021 at 2:12 AM Stephen Frost <sfrost@snowman.net> wrote:
> > In order to ensure that the data being returned from a foreign server
> > is consistent, postgres_fdw will only open one connection for a given
> > foreign server and will run all queries against that server sequentially
> > even if there are multiple foreign tables involved.  In such a case, it
> > may be more performant to disable this option to eliminate the overhead
> > associated with running queries asynchronously.
>
> Ok, I’ll merge this into the next version.

Stephen’s version would be much better than mine, so I updated the
patch as proposed except the first sentence.  If the foreign tables
are subject to different user mappings, multiple connections will be
opened, and queries will be performed in parallel.  So I expanded the
sentence a little bit, to avoid misunderstanding.  Attached is a new
version.

Best regards,
Etsuro Fujita

Attachment

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: naming of async_mode parameter
Next
From: Nitin Jadhav
Date:
Subject: Query about time zone patterns in to_char