Re: [GENERAL] a JOIN to a VIEW seems slow - Mailing list pgsql-general

From Merlin Moncure
Subject Re: [GENERAL] a JOIN to a VIEW seems slow
Date
Msg-id CAHyXU0wQC_vHnpV6=_XcCU73pKeMDXYQVMjtN-t2QRVQeM7V6Q@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] a JOIN to a VIEW seems slow  ("Frank Millman" <frank@chagford.com>)
Responses Re: [GENERAL] a JOIN to a VIEW seems slow
List pgsql-general
On Thu, Sep 21, 2017 at 1:51 AM, Frank Millman <frank@chagford.com> wrote:
> On 2017-09-18 Frank Millman wrote:
>>
>> Here are the timings for running the query on identical data sets using
>> Postgresql, Sql Server, and Sqlite3 -
>>
>> PostgreSQL -
>>     Method 1 - 0.28 sec
>>     Method 2 – 1607 sec, or 26 minutes
>>
>> Sql Server -
>>     Method 1 – 0.33 sec
>>     Method 2 – 1.8 sec
>>
>> Sqlite3 -
>>     Method 1 – 0.15 sec
>>     Method 2 – 1.0 sec
>>
>> It seems that Sql Server and Sqlite3 are able to analyse the ‘join’, and
>> execute an indexed read against the underlying physical tables.
>>
>
> I did not get any response to this, but I am still persevering, and feel
> that I am getting closer. Instead of waiting 26 minutes for a result, I
> realise that I can learn a lot by using EXPLAIN. This is what I have found
> out.

Something is not adding up here.  Can you EXPLAIN ANALYZE the 26 minute query?

merlin


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Peter Koukoulis
Date:
Subject: [GENERAL] hard parse?
Next
From: "David G. Johnston"
Date:
Subject: Re: [GENERAL] hard parse?