From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Cassiano, Marco <mcassiano@manord.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Performance of Postgresql Foreign Data Wrapper
Date: Fri, 30 Jan 2015 20:01:16 -0600
Message-ID: <54CC376C.9070508@BlueTreble.com> (raw)
In-Reply-To: <1361CEF686657C41A139AD8C3145632B44B33A8F@E2010-MB1.manord.com>
References: <1361CEF686657C41A139AD8C3145632B44B33A8F@E2010-MB1.manord.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 1/14/15 10:48 AM, Cassiano, Marco wrote:
> Both query were issued repeatedly to get rid of disk access and database
> connection overhead time.
>
> Activating duration and statement logging on the remote server I can see
> that the query issued through the fdw from the LOCAL SERVER
>
> is actually performed by opening a cursor :
I don't think the cursor is the issue here, but can you try running
those same commands directly on the remote server to make sure?
It looks like it's the fetch itself that's slow, which makes me wonder
if there's some network or other problem.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, mcassiano@manord.com
Subject: Re: Performance of Postgresql Foreign Data Wrapper
In-Reply-To: <54CC376C.9070508@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox