<!--
$Header: /cvsroot/pgsql-server/doc/src/sgml/info.sgml,v 1.20 2003/09/12 22:17:23 tgl Exp $
-->

<sect1 id="resources">
 <title>Further Information</title>

 <para>
  Besides the documentation, that is, this book, there are other
  resources about <productname>PostgreSQL</productname>:

  <variablelist>
   <varlistentry>
    <term>FAQs</term>
    <listitem>
     <para>
      The FAQ list <indexterm><primary>FAQ-Liste</></> contains
      continuously updated answers to frequently asked questions.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>READMEs</term>
    <listitem>
     <para>
      <filename>README</filename> files are available for most
      contributed packages.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>Web Site</term>
    <listitem>
     <para>
      The <ulink
      url="http://www.postgresql.org"><productname>PostgreSQL</productname>
      web site</ulink> carries details on the latest release and other
      information to make your work or play with
      <productname>PostgreSQL</productname> more productive.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>Mailing Lists</term>
    <listitem>
     <para>
      The mailing lists are a good place to have your questions
      answered, to share experiences with other users, and to contact
      the developers.  Consult the <productname>PostgreSQL</> web site
      for details.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>Yourself!</term>
    <listitem>
     <para>
      <productname>PostgreSQL</productname> is an open-source project.
      As such, it depends on the user community for ongoing support.
      As you begin to use <productname>PostgreSQL</productname>, you
      will rely on others for help, either through the documentation
      or through the mailing lists.  Consider contributing your
      knowledge back. Read the mailing lists and answer questions.  If
      you learn something which is not in the documentation, write it
      up and contribute it.  If you add features to the code,
      contribute them.
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </para>
</sect1>
