<!--

$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.16 2001/11/21 05:53:40 thomas Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.17 2003/01/19 00:13:28 momjian Exp $

-->

<chapter id="overview">

<para>

For information on the syntax and creation of rules in the

<productname>PostgreSQL</productname> system refer to

<citetitle>The PostgreSQL User's Guide</citetitle>.

<productname>PostgreSQL</productname> system refer to the

&cite-user;.

</para>

<sect2>

<!--

Documentation of the system catalogs, directed toward PostgreSQL developers

$Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.64 2002/12/17 17:41:30 momjian Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.65 2003/01/19 00:13:28 momjian Exp $

-->

<chapter id="catalogs">

<para>

New aggregate functions are registered with the <command>CREATE

AGGREGATE</command> command. See the<citetitle>Programmer's

Guide</citetitle> for moreinformation about writing aggregate

functions and the meaning ofthe transition functions, etc.

AGGREGATE</command> command. See the&cite-programmer; for more

information about writing aggregate functions and the meaning of

the transition functions, etc.

</para>

</sect1>

The <structname>pg_database</structname> catalog stores information

about the available databases. Databases are created with the

<command>CREATE DATABASE</command> command. Consult the

<citetitle>Administrator's Guide</citetitle>for details about the

meaning of some of theparameters.

&cite-admin;for details about the meaning of some of the

parameters.

</para>

<para>

<para>

This catalog defines groups and stores what users belong to what

groups. Groups are created with the <command>CREATE

GROUP</command> command. Consult the<citetitle>Administrator's

Guide</citetitle> for informationabout user permission management.

GROUP</command> command. Consult the&cite-admin; for information

about user permission management.

</para>

<para>

<structname>pg_language</structname> registers call interfaces or

languages in which you can write functions or stored procedures.

See under <command>CREATE LANGUAGE</command> and in the

<citetitle>Programmer's Guide</citetitle> for more information

about language handlers.

&cite-programmer; for more information about language handlers.

</para>

<table>

</para>

<para>

Operator classes are described at length in the

<citetitle>Programmer's Guide</citetitle>.

Operator classes are described at length in the &cite-programmer;.

</para>

<table>

<title>pg_operator</title>

<para>

See <command>CREATE OPERATOR</command> and the

<citetitle>Programmer's Guide</citetitle> for details on these

operator parameters.

See <command>CREATE OPERATOR</command> and the &cite-programmer;

for details on these operator parameters.

</para>

<table>

<para>

This catalog stores information about functions (or procedures).

The description of <command>CREATE FUNCTION</command> and the

<citetitle>Programmer's Guide</citetitle>contain more information

about the meaning ofsome fields.

&cite-programmer;contain more information about the meaning of

some fields.

</para>

<para>

</para>

<para>

The<citetitle>Administrator's Guide</citetitle>contains detailed

information about user andpermission management.

The&cite-admin;contains detailed information about user and

permission management.

</para>

<para>

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.30 2002/11/15 03:11:15 momjian Exp $ -->

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.31 2003/01/19 00:13:28 momjian Exp $ -->

<chapter id="charset">

<title>Localization</>

<productname>PostgreSQL</> speak their preferred language well.

If messages in your language is currently not available or fully

translated, your assistance would be appreciated. If you want to

help, refer to the<citetitle>Developer's Guide</>or write to the

developers'mailing list.

help, refer to the&cite-developer;or write to the developers'

mailing list.

</para>

</sect2>

</sect1>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.43 2003/01/06 03:18:26 momjian Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.44 2003/01/19 00:13:28 momjian Exp $

-->

<chapter id="client-authentication">

This record matches connection attempts using TCP/IP networks.

Note that TCP/IP connections are disabled unless the server is

started with the <option>-i</option> option or the

<literal>tcpip_socket</> <filename>postgresql.conf</>

configuration parameter is enabled.

<varname>tcpip_socket</> configuration parameter is enabled.

</para>

</listitem>

</varlistentry>

<para>

To be able make use of this option the server must be built

with SSL support enabled. Furthermore, SSL must be enabled by

enabling the option <literal>ssl</literal> in

<filename>postgresql.conf</filename> (see <xref

linkend="runtime-config">).

enabling the <varname>ssl</varname> configuration parameter

(see <xref linkend="runtime-config"> for more information).

</para>

</listitem>

</varlistentry>

must be zero for the record to match. (Of course IP addresses

can be spoofed but this consideration is beyond the scope of

<productname>PostgreSQL</productname>.) If you machine supports

IPv6, the default <filename>pg_hba.conf</> will have an IPv6

entry for <literal>localhost</>. You can add your own IPv6

IPv6, the default <filename>pg_hba.conf</>filewill have an

IPv6entry for <literal>localhost</>. You can add your own IPv6

entries to the file. IPv6 entries are used only for IPv6

connections.

</para>

</para>

<para>

<literal>trust</> authentication is appropriate and very convenient

for local connections on a single-user workstation. It is usually

<emphasis>not</> appropriate by itself on a multiuser machine.

However, you may be able to use <literal>trust</> even on a multiuser

machine, if you restrict access to the postmaster's socket file using

file-system permissions. To do this, set the parameter

<literal>trust</> authentication is appropriate and very

convenientfor local connections on a single-user workstation. It

is usually<emphasis>not</> appropriate by itself on a multiuser

machine.However, you may be able to use <literal>trust</> even

on a multiusermachine, if you restrict access to the postmaster's

socketfile using file-system permissions. To do this, set the

<varname>unix_socket_permissions</varname> (and possibly

<varname>unix_socket_group</varname>) in <filename>postgresql.conf</>,

as described in <xref linkend="runtime-config-general">. Or you could

set <varname>unix_socket_directory</varname> to place the socket file

in a suitably restricted directory.

<varname>unix_socket_group</varname>) configuration parameters as

described in <xref linkend="runtime-config-general">. Or you

could set the <varname>unix_socket_directory</varname>

configuration parameter to place the socket file in a suitably

restricted directory.

</para>

<para>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.22 2002/09/21 18:32:52 petere Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.23 2003/01/19 00:13:28 momjian Exp $

-->

<sect2 id="dfunc">

-bI:.../lib/postgres.exp -bE:foo.exp foo.o \e

-lm -lc 2>/dev/null

.fi

You should look at the <citetitle>PostgreSQL User's Manual</>

for an explanation of this

procedure.

You should look at the &cite-user; for an explanation of

this procedure.

-->

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.40 2002/11/15 03:11:16 momjian Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.41 2003/01/19 00:13:28 momjian Exp $

-->

<chapter id="ecpg">

FETCH <optional><replaceable>direction</></> <optional><replaceable>amount</></> IN|FROM <replaceable>cursor</replaceable>

</synopsis>

<indexterm><primary>Oracle</></>

<application>Oracle</application>, however, does not use the

<productname>Oracle</productname>, however, does not use the

keywords <literal>IN</literal> or <literal>FROM</literal>. This

feature cannot be added since it would create parsing conflicts.

</para>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.18 2002/11/03 01:31:32 momjian Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.19 2003/01/19 00:13:28 momjian Exp $

-->

<chapter id="extend">

</mediaobject>

</figure>

The<citetitle>Developer's Guide</citetitle>gives a more detailedexplanation

of thesecatalogs and their columns. However,

The&cite-developer;gives a more detailed explanation of these

catalogs and their columns. However,

<xref linkend="EXTEND-CATALOGS">

shows the major entities and their relationships

in the system catalogs. (Columns that do not refer

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.19 2002/01/07 02:29:12 petere Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.20 2003/01/19 00:13:28 momjian Exp $

-->

<sect1 id="history">

<title>AShort History of <productname>PostgreSQL</productname></title>

<title>ABrief History of <productname>PostgreSQL</productname></title>

<para>

The object-relational database management system now known as

released in June 1990 with the new rule system.

Version 3 appeared in 1991 and added support for multiple

storage managers, an improved query executor, and a

rewrittenrewriterule system. For the most part, subsequent

rewritten rule system. For the most part, subsequent

releases until <productname>Postgres95</productname> (see below)

focused on portability and reliability.

</para>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.17 2002/11/15 03:11:16 momjian Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.18 2003/01/19 00:13:28 momjian Exp $

-->

<sect1 id="resources">

Information for <productname>PostgreSQL</productname>

developers. This is intended for those who are contributing to

the <productname>PostgreSQL</productname> project; application

development information appears in the <citetitle>Programmer's

Guide</citetitle>.

development information appears in the &cite-programmer;.

</para>

</listitem>

</varlistentry>

<term>man pages</term>

<listitem>

<para>

The<citetitle>Reference Manual</citetitle>'s pages in the

traditional Unix manformat. There is no difference in content.

The&cite-reference;'s pages in the traditional Unix man

format. There is no difference in content.

</para>

</listitem>

</varlistentry>

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.127 2002/12/11 22:27:26 momjian Exp $ -->

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.128 2003/01/19 00:13:28 momjian Exp $ -->

<chapter id="installation">

<title><![%standalone-include[<productname>PostgreSQL</>]]>

internal header files and the server header files are installed

into private directories under

<varname>includedir</varname>.

See the<citetitle>Programmer's Guide</citetitle>for

information about how to get atthe header files for each interface.

See the&cite-programmer;for information about how to get at

the header files for each interface.

Finally, a private subdirectory will also be created, if appropriate,

under <varname>libdir</varname> for dynamically loadable modules.

</para>

<para>

The following is a quick summary of how to get <productname>PostgreSQL</> up and

running once installed. The <citetitle>Administrator's Guide</>

contains more information.

running once installed. The &cite-admin; contains more information.

</para>

<procedure>

</para>

<para>

The <citetitle>Tutorial</> should be your first reading if you

are completely new to <acronym>SQL</> databases.

If you are familiar with database concepts then you want to

proceed with the <citetitle>Administrator's Guide</citetitle>,

which contains information about how to set up the database

server, database users, and authentication.

The &cite-tutorial; should be your first reading if you are

completely new to <acronym>SQL</> databases. If you are

familiar with database concepts then you want to proceed with

the &cite-admin;, which contains information about how to set up

the database server, database users, and authentication.

</para>

</listitem>

<listitem>

<para>

Usually, you will want to modify your computer so that it will

automatically start the database server whenever it boots. Some

suggestions for this are in the <citetitle>Administrator's

Guide</citetitle>.

suggestions for this are in the &cite-admin;.

</para>

</listitem>

Run the regression tests against the installed server (using the

sequential test method). If you didn't run the tests before

installation, you should definitely do it now. This is also

explained in the<citetitle>Administrator's Guide</citetitle>.

explained in the&cite-admin;.

</para>

</listitem>