From: Jaime Casanova <systemguards@gmail.com>
To: J@planeti.biz <J@planeti.biz>
Cc: pgsql-sql@postgresql.org
Subject: Re: [PERFORM] Query optimization with X Y JOIN
Date: Thu, 26 Jan 2006 11:33:34 -0500
Message-ID: <c2d9e70e0601260833n69b9e4d1ibcaba926747c0311@mail.gmail.com> (raw)
In-Reply-To: <008001c62295$156b8fc0$0d310d05@fatchubby>
References: <786c2f6d0601260206k2201a548p48af7c7fc085d3b2@mail.gmail.com>
<005d01c6228f$3772dca0$0d310d05@fatchubby>
<43D8F4FD.4040703@modgraph-usa.com>
<008001c62295$156b8fc0$0d310d05@fatchubby>
On 1/26/06, J@planeti.biz <J@planeti.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 ;)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: systemguards@gmail.com, J@planeti.biz
Subject: Re: [PERFORM] Query optimization with X Y JOIN
In-Reply-To: <c2d9e70e0601260833n69b9e4d1ibcaba926747c0311@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox