Commit 66ef1b6e authored by Thomas G. Lockhart's avatar Thomas G. Lockhart

Minor changes to Fred Horsh's updates.

parent cb88fd19
This diff is collapsed.
<Sect1>
<Title>Resources</Title>
<Para>
This manual set is organized into several parts:
</Para>
<VariableList>
<VarListEntry>
<Term>Tutorial</Term>
<ListItem>
<Para>
An introduction for new users. Does not cover advanced features.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>User's Guide</Term>
<ListItem>
<Para>
General information for users, including available commands and data types.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Programmer's Guide</Term>
<ListItem>
<Para>
Advanced information for application programmers. Topics include
type and function extensibility, library interfaces, and application design issues.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Administrator's Guide</Term>
<ListItem>
<Para>
Installation and management information. List of supported machines.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Developer's Guide</Term>
<ListItem>
<Para>
Information for <ProductName>Postgres</ProductName> developers. This is intended
for those who are contributing to the <ProductName>Postgres</ProductName>
project; application development information should appear in the
<citetitle>Programmer's Guide</citetitle>.
Currently included in the <citetitle>Programmer's Guide</citetitle>.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Reference Manual</Term>
<ListItem>
<Para>
Detailed reference information on command syntax.
Currently included in the <citetitle>User's Guide</citetitle>.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
<Para>
In addition to this manual set, there are other resources to help you with
<ProductName>Postgres</ProductName> installation and use:
</Para>
<VariableList>
<VarListEntry>
<Term>man pages</Term>
<ListItem>
<Para>
The man pages have general information on command syntax.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>FAQs</Term>
<ListItem>
<Para>
The Frequently Asked Questions (FAQ) documents address both general issues
and some platform-specific issues.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>READMEs</Term>
<ListItem>
<Para>
README files are available for some contributed packages.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Web Site</Term>
<ListItem>
<Para>
The <ULink url="postgresql.org"><ProductName>Postgres</ProductName></ULink> web site has some information
not appearing in the distribution. There is a <ProductName>mhonarc</ProductName> catalog of mailing list traffic
which is a rich resource for many topics.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Mailing Lists</Term>
<ListItem>
<Para>
The <ULink url="http://www.PostgreSQL.ORG/mhonarc/pgsql-general/">pgsql-general</ULink>
mailing list is a good place to have user questions answered.
Other mailing lists are available; consult the Info Central section of the
PostgreSQL web site for details.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Yourself!</Term>
<ListItem>
<Para>
<ProductName>Postgres</ProductName> is an open source product.
As such, it depends on the user community for
ongoing support. As you begin to use <ProductName>Postgres</ProductName>,
you will rely on others
for help, either through the documentation or through the mailing lists.
Consider contributing your
knowledge back. If you learn something which is not in the documentation,
write it up and contribute it.
If you add features to the code, contribute it.</Para>
<Para>
Even those without a lot of experience can provide corrections and
minor changes in the documentation, and that is a good way to start.
The
<ULink url="http://www.PostgreSQL.ORG/mhonarc/pgsql-docs/">pgsql-docs</ULink>
mailing list is the place to get going.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</Sect1>
<sect1>
<title>Resources</title>
<para>
This manual set is organized into several parts:
</para>
<variablelist>
<varlistentry>
<term>Tutorial</term>
<listitem>
<para>
An introduction for new users. Does not cover advanced features.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>User's Guide</term>
<listitem>
<para>
General information for users, including available commands and data types.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Programmer's Guide</term>
<listitem>
<para>
Advanced information for application programmers. Topics include
type and function extensibility, library interfaces,
and application design issues.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Administrator's Guide</term>
<listitem>
<para>
Installation and management information. List of supported machines.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Developer's Guide</term>
<listitem>
<para>
Information for <productname>Postgres</productname> developers.
This is intended for those who are contributing to the
<productname>Postgres</productname> project;
application development information should appear in the
<citetitle>Programmer's Guide</citetitle>.
Currently included in the <citetitle>Programmer's Guide</citetitle>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Reference Manual</term>
<listitem>
<para>
Detailed reference information on command syntax.
Currently included in the <citetitle>User's Guide</citetitle>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
In addition to this manual set, there are other resources to help you with
<productname>Postgres</productname> installation and use:
</para>
<variablelist>
<varlistentry>
<term>man pages</term>
<listitem>
<para>
The man pages have general information on command syntax.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FAQs</term>
<listitem>
<para>
The Frequently Asked Questions (FAQ) documents address both general issues
and some platform-specific issues.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>READMEs</term>
<listitem>
<para>
README files are available for some contributed packages.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Web Site</term>
<listitem>
<para>
The
<ulink url="postgresql.org"><productname>Postgres</productname></ulink>
web site might have some information not appearing in the distribution.
There is a <productname>mhonarc</productname> catalog of mailing list traffic
which is a rich resource for many topics.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Mailing Lists</term>
<listitem>
<para>
The
<ulink url="mailto:pgsql-general@postgresql.org">pgsql-general</ulink>
(<ulink url="http://www.PostgreSQL.ORG/mhonarc/pgsql-general/">archive</ulink>)
mailing list is a good place to have user questions answered.
Other mailing lists are available; consult the Info Central section of the
PostgreSQL web site for details.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Yourself!</term>
<listitem>
<para>
<productname>Postgres</productname> is an open source product.
As such, it depends on the user community for ongoing support.
As you begin to use <productname>Postgres</productname>,
you will rely on others for help, either through the
documentation or through the mailing lists.
Consider contributing your knowledge back. If you learn something
which is not in the documentation, write it up and contribute it.
If you add features to the code, contribute it.
</para>
<para>
Even those without a lot of experience can provide corrections and
minor changes in the documentation, and that is a good way to start.
The
<ulink url="mailto:pgsql-docs@postgresql.org">pgsql-docs</ulink>
(<ulink url="http://www.PostgreSQL.ORG/mhonarc/pgsql-docs/">archive</ulink>)
mailing list is the place to get going.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"./reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:"/usr/lib/sgml/catalog"
sgml-local-ecat-files:nil
End:
-->
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment