Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCf5w-000244-PI for pgsql-docs@arkaria.postgresql.org; Mon, 04 Mar 2013 23:47:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UCf5w-0008Mv-8P for pgsql-docs@arkaria.postgresql.org; Mon, 04 Mar 2013 23:47:00 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCf5v-0008M0-0Q for pgsql-docs@postgresql.org; Mon, 04 Mar 2013 23:46:59 +0000 Received: from mail-oa0-f53.google.com ([209.85.219.53]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCf5s-0000vz-NB for pgsql-docs@postgresql.org; Mon, 04 Mar 2013 23:46:58 +0000 Received: by mail-oa0-f53.google.com with SMTP id m1so9968522oag.26 for ; Mon, 04 Mar 2013 15:46:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=NJ0bkxUjjYcGzUuKwSLRhTsycm4S44z/qbVQZ7nguoU=; b=SFlFdnHY9HL7sdgz2KU0EoZx9K3EWVHW75QpYO5WqSzAhw/PCsgw0q7GeAmnzkHP1I I69KsTEt/awN1xVgqsy6y9KqPWdKt3ELWFV0We/YgkJwfZpjC2FQM8bVGAiirWrdBy/G 96SAa7YJCRPW2m7smq9OsGThJdSn3yp/eUjzcWN54pfsgURwKwElsWgxz/9mJFQ8alwo /cvFNiy1MXbRz/0e1Ole8AX0eTq4Zm/BnBa/DbrF4Hvxrl5p+J09rtxwB+Sw+hgl4poV liAr2Bzv6r3Ua99D407wch2mPswhTff/LOv8AukYhqiIdCZ1X9fnwIGBCLzWhmkA2G21 8kyA== MIME-Version: 1.0 X-Received: by 10.60.27.136 with SMTP id t8mr16878609oeg.92.1362440815825; Mon, 04 Mar 2013 15:46:55 -0800 (PST) Received: by 10.182.104.6 with HTTP; Mon, 4 Mar 2013 15:46:55 -0800 (PST) Date: Mon, 4 Mar 2013 20:46:55 -0300 Message-ID: Subject: Doc Questions From: Tiago Barabasz To: pgsql-docs@postgresql.org Content-Type: multipart/alternative; boundary=e89a8fb1fe2adadac104d721f8da X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --e89a8fb1fe2adadac104d721f8da Content-Type: text/plain; charset=ISO-8859-1 Hi, I have two questions about the documentation. 1. In section "44.3 The Parser Stage", it is said that the file scan.l is responsible for recognizing SQL keywords... however, I downloaded the Postgres source and it seems like all the SQL keywords are in the file gram.y, is this correct? Link to what I'm saying: http://www.postgresql.org/docs/9.2/interactive/parser-stage.html 2. In section "44.5. Planner/Optimizer", it is said that the planner works internally with *paths* and only after the shortest *path* is determined a *plan tree* is created. Shouldn't the following section "44.5.1 Generating Possible Plans" be called "44.5.1 Generating Possible Paths"? Link to what I'm saying: http://www.postgresql.org/docs/9.2/interactive/planner-optimizer.html Thanks in advance, Regards, -- Tiago Barabasz --e89a8fb1fe2adadac104d721f8da Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I have two questions about the documentation.

1.=A0 In section &= quot;44.3 The Parser Stage", it is said that the file scan.l is respon= sible for recognizing SQL keywords... however, I downloaded the Postgres so= urce and it seems like all the SQL keywords are in the file gram.y, is this= correct?
=A0 =A0 Link to what I'm saying: http://www.postgresql.org/docs/9.2/i= nteractive/parser-stage.html =A0=A0

2. In section "44.5. P= lanner/Optimizer", it is said that the planner works internally with <= i>paths and only after the shortest path is determined
a plan tree is created. Shouldn't the following section "44= .5.1 Generating Possible Plans" be called "44.5.1 Generating Poss= ible Paths"?
=A0=A0=A0 Link to what I'm saying: http://w= ww.postgresql.org/docs/9.2/interactive/planner-optimizer.html

Thanks in advance,

Regards,

--
Tiago Barabasz --e89a8fb1fe2adadac104d721f8da--