| From: | Joe Van Dyk <joe(at)tanga(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Joining against a view that uses an aggregate - performance issue |
| Date: | 2013-03-09 00:17:55 |
| Message-ID: | CACfv+pLYOiJgabHBcuyLHrrirFqrH5O16xD0H35t99c-CLXQfA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
andres on #postgresql says that making #2 use a faster plan shouldn't be
hard, but he doesn't seem #3 happening.
I was surprised about #2 not being faster, andres said "Afaics its this
restriction: "1. The qual must not contain any subselects (mainly because
I'm not sure it will work correctly: sublinks will already have been
transformed into subplans in the qual, but not in the subquery)." in
qual_is_pushdown_safe"
Not sure if there's anything to be done here, just thought I'd post in case
anyone has any ideas. In an ideal world, I'd be able to write version #3.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Van Dyk | 2013-03-09 00:22:35 | Re: Joining against a view that uses an aggregate - performance issue |
| Previous Message | Bradley Russell | 2013-03-08 21:14:25 | Re: stored procedure slower when called through c client than pgadmin |