Re: What constitutes a complex query

From: "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: Justin <justin(at)emproshunts(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: What constitutes a complex query
Date: 2008-05-06 16:58:39
Message-ID: 396486430805060958x31dd63ffu994493f68d8e828f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, May 6, 2008 at 9:41 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> I'd say that the use of correlated subqueries qualifies a query as
> complicated. Joining on non-usual pk-fk stuff. the more you're
> mashing one set of data against another, and the odder the way you
> have to do it, the more complex the query becomes.

I would add that data analysis queries that have multiple level of
aggregation analysis can be complicated also.

For example, in a table of racer times find the average time for each
team while only counting teams whom at least have greater than four
team members and produce an ordered list displaying the ranking for
each team according to their average time.

--
Regards,
Richard Broersma Jr.

Visit the Los Angles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Justin 2008-05-06 17:22:11 Re: need to speed up query
Previous Message Steve Atkins 2008-05-06 16:56:16 Re: What constitutes a complex query