<note>

<para>

</para>

</note>

</para>

<para>

The <firstterm>parser</firstterm> defined in

<filename>gram.y</filename> and <filename>scan.l</filename> is

and <application>lex</application>.

</para>

</listitem>

The parser has to check the query string (which arrives as

plain ASCII text) for valid syntax. If the syntax is correct a

<firstterm>parse tree</firstterm> is built up and handed back otherwise an error is

tools <application>lex</application> and <application>yacc</application>

are used.

</para>

somewhat clearer.

In database jargon, <ProductName>Postgres</ProductName> uses a simple "process

per-user" client/server model. A <ProductName>Postgres</ProductName> session

<ItemizedList>

<ListItem>

have to be a special user (e.g., a user named

"postgres"), although many systems are installed that way.

Furthermore, the <ProductName>Postgres</ProductName> superuser should

case, all files relating to a database should belong to

this <ProductName>Postgres</ProductName> superuser.

</Para>

somewhat clearer.

In database jargon, <ProductName>Postgres</ProductName> uses a simple "process

per-user" client/server model. A <ProductName>Postgres</ProductName> session

</Para>

<ItemizedList>

have to be a special user (e.g., a user named

"postgres"). Furthermore, the <ProductName>Postgres</ProductName> superuser

should

case, all files relating to a database should belong to

this <ProductName>Postgres</ProductName> superuser.

</Para>