Date: Sun, 25 Nov 2018 07:30:02 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: explain analyze faster then query
Message-ID: <20181125133002.GP10913@telsasoft.com>
References: 
 <CA+t6e1nb40u+EN3wUjFc6CzvkZ+0vjFr=dX+Y4QmA6tAwXLWEg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CA+t6e1nb40u+EN3wUjFc6CzvkZ+0vjFr=dX+Y4QmA6tAwXLWEg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

Cc: pgsql-performance@lists.postgresql.org,
	pgsql-admin@lists.postgresql.org

Please avoid simultaneously sending the same question to multiple lists.

It means that people can't see each others replies and everything that implies.

On Sun, Nov 25, 2018 at 03:08:33PM +0200, Mariel Cherkassky wrote:
> However when I run the query without the explain analyze it takes forever
> to run it(More then two hours).
> Is there a possibility that it is related to fetching or something like
> that ?

If it's a remote database, I expect that's why.
Maybe you can test by running the query on the DB server.
Or by running another variant of the query, such as:

WITH x AS (QUERY GOES HERE) SELECT 1;

which returns only one row but after having executed the query behind CTE, as
optimization fence.

Justin