Postgres Pro
Downloads
Home   >   mailing lists

Re: LIMIT OFFSET with DB view vs plain SQL - Mailing list pgsql-admin

From Raj Gandhi
Subject Re: LIMIT OFFSET with DB view vs plain SQL
Date
Msg-id CALU_HCPRYnxGdEJnY6AySAyMHTxyHMF=uOv40Esfes5cWg+qPQ@mail.gmail.com
Whole thread Raw
In response to LIMIT OFFSET with DB view vs plain SQL  (Raj Gandhi <raj01gandhi@gmail.com>)
Responses Re: LIMIT OFFSET with DB view vs plain SQL  (Merlin Moncure <mmoncure@gmail.com>)
Re: LIMIT OFFSET with DB view vs plain SQL  (Merlin Moncure <mmoncure@gmail.com>)
Re: LIMIT OFFSET with DB view vs plain SQL  (Ramón Bastidas <ramon.r.bastidas@gmail.com>)
Re: LIMIT OFFSET with DB view vs plain SQL  (Ramón Bastidas <ramon.r.bastidas@gmail.com>)
List pgsql-admin
Tree view
+ pgsql-performance 

On Thu, Mar 28, 2019 at 6:41 PM Raj Gandhi <raj01gandhi@gmail.com> wrote:

Hi everyone,

 

I’m using LIMIT offset with DB view. Looks like query planner is applying the LIMIT for DB view at the end after processing all rows.

When running same SQL that was used to create the DB view, LIMIT is applied earlier so the query is much faster.

 

Explain plan using DB view

https://explain.depesz.com/s/gzjQ

 

Explain plan using raw SQL

https://explain.depesz.com/s/KgwO

 

In both tests LIMIT was 100 with offset  = 0.

Is there any way to force DB view to apply limit earlier?

 

Thanks,

Raj

pgsql-admin by date:

Previous
From: Raj Gandhi
Date:
Subject: LIMIT OFFSET with DB view vs plain SQL
Next
From: Laurenz Albe
Date:
Subject: Re: LIMIT OFFSET with DB view vs plain SQL