From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | "J(at)planeti(dot)biz" <J(at)planeti(dot)biz> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [PERFORM] Query optimization with X Y JOIN |
Date: | 2006-01-26 16:33:34 |
Message-ID: | c2d9e70e0601260833n69b9e4d1ibcaba926747c0311@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance pgsql-sql |
On 1/26/06, J(at)planeti(dot)biz <J(at)planeti(dot)biz> wrote:
> If I want my database to go faster, due to X then I would think that the
> issue is about performance. I wasn't aware of a paticular constraint on X.
>
> I have more that a rudementary understanding of what's going on here, I was
> just hoping that someone could shed some light on the basic principal of
> this JOIN command and its syntax. Most people I ask, don't give me straight
> answers and what I have already read on the web is not very helpful thus
> far.
http://www.postgresql.org/docs/current/static/sql-select.html
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-01-26 16:34:11 | Re: Query optimization with X Y JOIN |
Previous Message | J | 2006-01-26 16:25:12 | Re: Query optimization with X Y JOIN |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-01-26 16:34:11 | Re: Query optimization with X Y JOIN |
Previous Message | J | 2006-01-26 16:25:12 | Re: Query optimization with X Y JOIN |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-01-26 16:34:11 | Re: Query optimization with X Y JOIN |
Previous Message | J | 2006-01-26 16:25:12 | Re: Query optimization with X Y JOIN |