| From: | Raj Gandhi <raj01gandhi(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | LIMIT OFFSET with DB view vs plain SQL |
| Date: | 2019-03-28 22:41:13 |
| Message-ID: | CALU_HCMxM5m-Sxsn3fwhqwu23b3O2q+Rviv-fxdJM1EXG=A3fg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raj Gandhi | 2019-03-28 22:43:45 | Re: LIMIT OFFSET with DB view vs plain SQL |
| Previous Message | Shreeyansh Dba | 2019-03-28 15:37:33 | Re: Case Insensitive |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raj Gandhi | 2019-03-28 22:43:45 | Re: LIMIT OFFSET with DB view vs plain SQL |
| Previous Message | Sumedh Pathak | 2019-03-28 16:26:23 | Re: Scale out postgresql |