On Tue, May 6, 2008 at 11:23 AM, Justin <[EMAIL PROTECTED]> wrote:
>
>
> Craig James wrote:
>
> > Justin wrote:
> >
> > > This falls under the stupid question and i'm just curious what other
> people think what makes a query complex?
> > >
> >
> > There are two kinds:
> >
> > 1. Hard for Postgres
Craig James wrote:
Justin wrote:
This falls under the stupid question and i'm just curious what other
people think what makes a query complex?
There are two kinds:
1. Hard for Postgres to get the answer.
this one
2. Hard for a person to comprehend.
Which do you mean?
Craig
--
Sent v
On Tue, May 6, 2008 at 9:41 AM, Scott Marlowe <[EMAIL PROTECTED]> 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
On May 6, 2008, at 8:45 AM, Justin wrote:
This falls under the stupid question and i'm just curious what other
people think what makes a query complex?
If I know in advance exactly how the planner will plan the query (and
be right), it's a simple query.
Otherwise it's a complex query.
A
On Tue, May 6, 2008 at 9:45 AM, Justin <[EMAIL PROTECTED]> wrote:
> This falls under the stupid question and i'm just curious what other people
> think what makes a query complex?
Well, as mentioned, there's two kinds. some that look big and ugly
are actually just shovelling data with no fancy in
Justin wrote:
This falls under the stupid question and i'm just curious what other
people think what makes a query complex?
There are two kinds:
1. Hard for Postgres to get the answer.
2. Hard for a person to comprehend.
Which do you mean?
Craig
--
Sent via pgsql-performance mailing list (
This falls under the stupid question and i'm just curious what other
people think what makes a query complex?
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
