head	1.27;
access;
symbols
	REL9_0_0:1.27
	REL9_1_ALPHA1:1.27
	REL9_0_RC1:1.27
	REL9_0_BETA4:1.27
	REL9_0_STABLE:1.27.0.14
	REL9_0_BETA3:1.27
	REL9_0_BETA2:1.27
	REL7_4_29:1.20.2.1
	REL8_0_25:1.21.4.1
	REL8_1_21:1.23.2.1
	REL8_2_17:1.24.2.1
	REL8_3_11:1.26
	REL8_4_4:1.27
	REL9_0_BETA1:1.27
	REL9_0_ALPHA5_BRANCH:1.27.0.12
	REL9_0_ALPHA5:1.27
	REL7_4_28:1.20.2.1
	REL8_0_24:1.21.4.1
	REL8_1_20:1.23.2.1
	REL8_2_16:1.24.2.1
	REL8_3_10:1.26
	REL8_4_3:1.27
	REL9_0_ALPHA4:1.27
	REL9_0_ALPHA4_BRANCH:1.27.0.10
	REL8_5_ALPHA3:1.27
	REL8_5_ALPHA3_BRANCH:1.27.0.8
	REL7_4_27:1.20.2.1
	REL8_0_23:1.21.4.1
	REL8_1_19:1.23.2.1
	REL8_2_15:1.24.2.1
	REL8_3_9:1.26
	REL8_4_2:1.27
	REL8_5_ALPHA2:1.27
	REL8_5_ALPHA2_BRANCH:1.27.0.6
	REL7_4_26:1.20.2.1
	REL8_0_22:1.21.4.1
	REL8_1_18:1.23.2.1
	REL8_2_14:1.24.2.1
	REL8_3_8:1.26
	REL8_4_1:1.27
	REL8_5_ALPHA1:1.27
	REL8_5_ALPHA1_BRANCH:1.27.0.4
	REL8_4_STABLE:1.27.0.2
	REL8_4_0:1.27
	REL8_4_RC2:1.27
	REL8_4_RC1:1.27
	REL8_4_BETA2:1.27
	REL8_4_BETA1:1.26
	REL7_4_25:1.20.2.1
	REL8_0_21:1.21.4.1
	REL8_1_17:1.23.2.1
	REL8_2_13:1.24.2.1
	REL8_3_7:1.26
	REL7_4_24:1.20.2.1
	REL8_0_20:1.21.4.1
	REL8_1_16:1.23.2.1
	REL8_2_12:1.24.2.1
	REL8_3_6:1.26
	REL7_4_23:1.20.2.1
	REL8_0_19:1.21.4.1
	REL8_1_15:1.23.2.1
	REL8_2_11:1.24.2.1
	REL8_3_5:1.26
	REL7_4_22:1.20.2.1
	REL8_0_18:1.21.4.1
	REL8_1_14:1.23.2.1
	REL8_2_10:1.24.2.1
	REL8_3_4:1.26
	REL7_4_21:1.20.2.1
	REL8_0_17:1.21.4.1
	REL8_1_13:1.23.2.1
	REL8_2_9:1.24.2.1
	REL8_3_3:1.26
	REL7_4_20:1.20.2.1
	REL8_0_16:1.21.4.1
	REL8_1_12:1.23.2.1
	REL8_2_8:1.24.2.1
	REL8_3_2:1.26
	REL8_2_7:1.24.2.1
	REL8_3_1:1.26
	REL8_3_STABLE:1.26.0.2
	REL8_3_0:1.26
	REL8_3_RC2:1.26
	REL7_3_21:1.16
	REL7_4_19:1.20.2.1
	REL8_0_15:1.21.4.1
	REL8_1_11:1.23.2.1
	REL8_2_6:1.24.2.1
	REL8_3_RC1:1.25
	REL8_3_BETA4:1.25
	REL8_3_BETA3:1.25
	REL8_3_BETA2:1.25
	REL8_3_BETA1:1.25
	REL7_3_20:1.16
	REL7_4_18:1.20.2.1
	REL8_0_14:1.21.4.1
	REL8_1_10:1.23.2.1
	REL8_2_5:1.24.2.1
	REL7_3_19:1.16
	REL7_4_17:1.20
	REL8_0_13:1.21
	REL8_1_9:1.23
	REL8_2_4:1.24
	REL8_0_12:1.21
	REL8_1_8:1.23
	REL8_2_3:1.24
	REL7_3_18:1.16
	REL7_4_16:1.20
	REL8_0_11:1.21
	REL8_1_7:1.23
	REL8_2_2:1.24
	REL8_0_10:1.21
	REL8_1_6:1.23
	REL8_2_1:1.24
	REL7_4_15:1.20
	REL7_3_17:1.16
	REL8_2_STABLE:1.24.0.2
	REL8_2_0:1.24
	REL8_2_RC1:1.24
	REL8_2_BETA3:1.24
	REL8_2_BETA2:1.24
	REL8_1_5:1.23
	REL8_0_9:1.21
	REL7_4_14:1.20
	REL7_3_16:1.16
	REL8_2_BETA1:1.24
	REL7_3_15:1.16
	REL7_4_13:1.20
	REL8_0_8:1.21
	REL8_1_4:1.23
	REL7_3_14:1.16
	REL7_4_12:1.20
	REL8_0_7:1.21
	REL8_1_3:1.23
	REL7_3_13:1.16
	REL7_4_11:1.20
	REL8_0_6:1.21
	REL8_1_2:1.23
	REL7_3_12:1.16
	REL7_4_10:1.20
	REL8_0_5:1.21
	REL8_1_1:1.23
	REL8_1_STABLE:1.23.0.2
	REL8_1_0:1.23
	REL8_1_0RC1:1.23
	REL8_1_0BETA4:1.23
	REL8_1_0BETA3:1.23
	REL7_3_11:1.16
	REL7_4_9:1.20
	REL8_0_4:1.21
	REL8_1_0BETA2:1.23
	REL8_1_0BETA1:1.23
	REL7_2_8:1.15
	REL7_3_10:1.16
	REL7_4_8:1.20
	REL8_0_3:1.21
	REL8_0_2:1.21
	REL7_2_7:1.15
	REL7_3_9:1.16
	REL7_4_7:1.20
	REL8_0_1:1.21
	REL8_0_STABLE:1.21.0.4
	REL8_0_0:1.21.0.2
	REL8_0_0RC5:1.21
	REL8_0_0RC4:1.21
	REL8_0_0RC3:1.21
	REL8_0_0RC2:1.21
	REL8_0_0RC1:1.21
	REL8_0_0BETA5:1.21
	REL8_0_0BETA4:1.21
	REL7_4_6:1.20
	REL7_3_8:1.16
	REL7_2_6:1.15
	REL8_0_0BETA3:1.21
	REL8_0_0BETA2:1.21
	REL7_2_5:1.15
	REL7_4_5:1.20
	REL7_3_7:1.16
	REL7_4_4:1.20
	REL8_0_0BETA1:1.21
	REL7_4_3:1.20
	REL7_4_2:1.20
	REL7_3_6:1.16
	REL7_4_1:1.20
	REL7_3_5:1.16
	REL7_4:1.20
	REL7_4_RC2:1.20
	REL7_4_STABLE:1.20.0.2
	REL7_4_RC1:1.20
	REL7_4_BETA5:1.20
	REL7_4_BETA4:1.20
	REL7_4_BETA3:1.20
	REL7_4_BETA2:1.18
	WIN32_DEV:1.18.0.2
	REL7_4_BETA1:1.18
	REL7_3_4:1.16
	REL7_3_2:1.16
	REL7_2_4:1.15
	REL7_3_STABLE:1.16.0.2
	REL7_2_3:1.15
	REL7_2_STABLE:1.15.0.2
	REL7_2:1.15
	REL7_2_RC2:1.15
	REL7_2_RC1:1.15
	REL7_2_BETA5:1.15
	REL7_2_BETA4:1.15
	REL7_2_BETA3:1.13
	REL7_2_BETA2:1.12
	REL7_2_BETA1:1.12
	REL7_1_2:1.11
	REL7_1_STABLE:1.11.0.2
	REL7_1_BETA:1.9
	REL7_1_BETA3:1.10
	REL7_1_BETA2:1.10
	REL7_1:1.11
	REL7_0_PATCHES:1.8.0.2
	REL7_0:1.6
	REL6_5_PATCHES:1.5.0.2
	REL6_5:1.5
	REL6_4:1.2.0.2;
locks; strict;
comment	@# @;


1.27
date	2009.04.27.16.27.35;	author momjian;	state Exp;
branches;
next	1.26;

1.26
date	2008.01.09.02.37.45;	author momjian;	state Exp;
branches;
next	1.25;

1.25
date	2007.05.21.15.11.12;	author petere;	state Exp;
branches;
next	1.24;

1.24
date	2006.03.10.19.10.48;	author momjian;	state Exp;
branches
	1.24.2.1;
next	1.23;

1.23
date	2005.04.09.03.52.43;	author momjian;	state Exp;
branches
	1.23.2.1;
next	1.22;

1.22
date	2005.03.31.03.54.38;	author momjian;	state Exp;
branches;
next	1.21;

1.21
date	2003.11.29.19.51.37;	author pgsql;	state Exp;
branches
	1.21.4.1;
next	1.20;

1.20
date	2003.09.12.22.17.23;	author tgl;	state Exp;
branches
	1.20.2.1;
next	1.19;

1.19
date	2003.09.08.23.02.28;	author petere;	state Exp;
branches;
next	1.18;

1.18
date	2003.01.19.00.13.28;	author momjian;	state Exp;
branches;
next	1.17;

1.17
date	2002.11.15.03.11.16;	author momjian;	state Exp;
branches;
next	1.16;

1.16
date	2002.10.24.17.48.54;	author petere;	state Exp;
branches;
next	1.15;

1.15
date	2001.11.28.20.49.10;	author petere;	state Exp;
branches;
next	1.14;

1.14
date	2001.11.21.05.53.41;	author thomas;	state Exp;
branches;
next	1.13;

1.13
date	2001.11.08.23.37.50;	author petere;	state Exp;
branches;
next	1.12;

1.12
date	2001.09.02.23.27.49;	author petere;	state Exp;
branches;
next	1.11;

1.11
date	2001.02.03.19.03.26;	author petere;	state Exp;
branches;
next	1.10;

1.10
date	2000.12.22.21.51.57;	author petere;	state Exp;
branches;
next	1.9;

1.9
date	2000.09.29.20.21.34;	author petere;	state Exp;
branches;
next	1.8;

1.8
date	2000.05.11.17.32.32;	author momjian;	state Exp;
branches;
next	1.7;

1.7
date	2000.05.11.15.18.13;	author thomas;	state Exp;
branches;
next	1.6;

1.6
date	2000.03.31.03.27.40;	author thomas;	state Exp;
branches;
next	1.5;

1.5
date	99.06.23.06.12.31;	author thomas;	state Exp;
branches;
next	1.4;

1.4
date	99.06.21.15.23.58;	author momjian;	state Exp;
branches;
next	1.3;

1.3
date	98.12.29.02.24.16;	author thomas;	state Exp;
branches;
next	1.2;

1.2
date	98.10.30.19.36.58;	author thomas;	state Exp;
branches;
next	1.1;

1.1
date	98.09.30.05.41.44;	author thomas;	state Exp;
branches;
next	;

1.20.2.1
date	2007.05.21.15.00.57;	author petere;	state Exp;
branches;
next	;

1.21.4.1
date	2007.05.21.15.06.44;	author petere;	state Exp;
branches;
next	;

1.23.2.1
date	2007.05.21.15.09.46;	author petere;	state Exp;
branches;
next	;

1.24.2.1
date	2007.05.21.15.10.20;	author petere;	state Exp;
branches;
next	;


desc
@@


1.27
log
@Proofreading adjustments for first two parts of documentation (Tutorial
and SQL).
@
text
@<!-- $PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.26 2008/01/09 02:37:45 momjian 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>Wiki</term>
    <listitem>
     <para>
      The <productname>PostgreSQL</productname> <ulink
      url="http://wiki.postgresql.org">wiki</ulink> contains the project's <ulink
      url="http://wiki.postgresql.org/wiki/Frequently_Asked_Questions">FAQ</>
      (Frequently Asked Questions) list, <ulink
      url="http://wiki.postgresql.org/wiki/Todo">TODO</> list, and
      detailed information about many more topics.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>Web Site</term>
    <listitem>
     <para>
      The <productname>PostgreSQL</productname> 
      <ulink url="http://www.postgresql.org">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>
@


1.26
log
@Remove mention of /contrib README files from documentation because files
are moved to SGML.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.25 2007/05/21 15:11:12 petere Exp $ -->
d11 1
d13 1
a13 1
    <term>FAQs</term>
d16 6
a21 2
      The FAQ list <indexterm><primary>FAQ</></> contains
      continuously updated answers to frequently asked questions.
@


1.25
log
@Fix spurious German index entry
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.24 2006/03/10 19:10:48 momjian Exp $ -->
a21 10
    <term>READMEs</term>
    <listitem>
     <para>
      <filename>README</filename> files are available for most
      contributed packages.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
@


1.24
log
@Make $PostgreSQL CVS tags consistent for SGML files.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/advanced.sgml,v 1.49 2005/04/09 03:52:43 momjian Exp $ -->
d15 1
a15 1
      The FAQ list <indexterm><primary>FAQ-Liste</></> contains
@


1.24.2.1
log
@Fix spurious German index entry
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.24 2006/03/10 19:10:48 momjian Exp $ -->
d15 1
a15 1
      The FAQ list <indexterm><primary>FAQ</></> contains
@


1.23
log
@We don't put URL's in ulink's because the URL is always generated, but
we can put words in ulink and the URL will still be printed.

per Peter
@
text
@d1 1
a1 3
<!--
$PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.22 2005/03/31 03:54:38 momjian Exp $
-->
@


1.23.2.1
log
@Fix spurious German index entry
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.23 2005/04/09 03:52:43 momjian Exp $
d17 1
a17 1
      The FAQ list <indexterm><primary>FAQ</></> contains
@


1.22
log
@Adjust SGML ulink tags to the URL is always displayed in our printed docs.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.21 2003/11/29 19:51:37 pgsql Exp $
d37 2
a38 2
      The <productname>PostgreSQL</productname> web site,
      <ulink url="http://www.postgresql.org"></ulink>,
@


1.21
log
@
$Header: -> $PostgreSQL Changes ...
@
text
@d2 1
a2 1
$PostgreSQL: /cvsroot/pgsql-server/doc/src/sgml/info.sgml,v 1.20 2003/09/12 22:17:23 tgl Exp $
d37 3
a39 3
      The <ulink
      url="http://www.postgresql.org"><productname>PostgreSQL</productname>
      web site</ulink> carries details on the latest release and other
@


1.21.4.1
log
@Fix spurious German index entry
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/info.sgml,v 1.21 2003/11/29 19:51:37 pgsql Exp $
d17 1
a17 1
      The FAQ list <indexterm><primary>FAQ</></> contains
@


1.20
log
@Update obsolete examples of error messages; various other minor editing.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/info.sgml,v 1.19 2003/09/08 23:02:28 petere Exp $
@


1.20.2.1
log
@Fix spurious German index entry
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.20 2003/09/12 22:17:23 tgl Exp $
d17 1
a17 1
      The FAQ list <indexterm><primary>FAQ</></> contains
@


1.19
log
@Update preface.

Use question marks rather than brackets to delimit optional elements in
Tcl synopses.

Fix stylesheet misfeature leading to excessively long cross-reference text
when linking to a different "part".

Remove <body> attributes -- CSS stylesheets should handle that.

Improve bibliography formatting.

Add fast-forward links for more convenient navigation.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/info.sgml,v 1.18 2003/01/19 00:13:28 momjian Exp $
d27 1
a27 1
      <filename>README</filename> files are available for some
@


1.18
log
@This patch includes a lot of minor cleanups to the SGML documentation,
including:

- replacing all the appropriate usages of <citetitle>PostgreSQL
...</citetitle> with &cite-user;, &cite-admin;, and so on

- fix an omission in the EXECUTE documentation

- add some more text to the EXPLAIN documentation

- improve the PL/PgSQL RETURN NEXT documentation (more work to do here)

- minor markup fixes


Neil Conway
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/info.sgml,v 1.17 2002/11/15 03:11:16 momjian Exp $
d6 1
a6 1
 <title>Overview of Documentation Resources</title>
d9 2
a10 2
  The <productname>PostgreSQL</> documentation is organized into
  several books:
a13 83
    <term>&cite-tutorial;</term>
    <listitem>
     <para>
      An informal introduction for new users.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>&cite-user;</term>
    <listitem>
     <para>
      Documents the <acronym>SQL</acronym> query language environment,
      including data types and functions, as well as user-level
      performance tuning.  Every <productname>PostgreSQL</> user
      should read this.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>&cite-admin;</term>
    <listitem>
     <para>
      Installation and server management information.  Everyone who
      runs a <productname>PostgreSQL</> server, either for personal
      use or for other users, needs to read this.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>&cite-programmer;</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>&cite-reference;</term>
    <listitem>
     <para>
      Reference pages for <acronym>SQL</acronym> command syntax, and
      client and server programs.  This book is auxiliary to the
      User's, Administrator's, and Programmer's Guides.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
    <term>&cite-developer;</term>
    <listitem>
     <para>
      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 &cite-programmer;.
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </para>

 <para>
  In addition to this manual set, there are other resources to help you with
  <productname>PostgreSQL</productname> installation and use:

  <variablelist>
   <varlistentry>
    <term>man pages</term>
    <listitem>
     <para>
      The &cite-reference;'s pages in the traditional Unix man
      format. There is no difference in content.
     </para>
    </listitem>
   </varlistentry>

   <varlistentry>
d17 2
a18 2
      Frequently Asked Questions (FAQ) lists document both general issues
      and some platform-specific issues.
d27 2
a28 1
      README files are available for some contributed packages.
d39 2
a40 2
      web site</ulink> carries details on the latest release, upcoming
      features, and other information to make your work or play with
d52 2
a53 4
      the developers.  Consult the <ulink
      url="http://www.postgresql.org/users-lounge/">User's
      Lounge</ulink> section of the <productname>PostgreSQL</>
      web site for details.
d62 1
a62 1
      <productname>PostgreSQL</productname> is an open-source effort.
d67 4
a70 10
      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 them.
     </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 <email>pgsql-docs@@postgresql.org</email> mailing
      list is the place to get going.
a76 17

<!-- 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:
-->
@


1.17
log
@SGML improvements.

Neil Conway
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/info.sgml,v 1.16 2002/10/24 17:48:54 petere Exp $
d74 1
a74 2
      development information appears in the <citetitle>Programmer's
      Guide</citetitle>.
d90 2
a91 2
      The <citetitle>Reference Manual</citetitle>'s pages in the
      traditional Unix man format.  There is no difference in content.
@


1.16
log
@Add introductory sections explaining what each book is about.  Remove Y2K
statement.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/info.sgml,v 1.15 2001/11/28 20:49:10 petere Exp $
d9 2
a10 1
  The PostgreSQL documentation is organized into several books:
d26 4
a29 3
      Documents the SQL query language environment, including data
      types and functions, as well as user-level performance tuning.
      Every PostgreSQL user should read this.
d39 2
a40 2
      runs a PostgreSQL server, either for personal use or for other
      users, needs to read this.
d60 3
a62 3
      Reference pages for SQL command syntax, and client and server
      programs.  This book is auxiliary to the User's,
      Administrator's, and Programmer's Guides.
@


1.15
log
@proof-reading
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.14 2001/11/21 05:53:41 thomas Exp $
d6 1
a6 1
 <title>Documentation Resources</title>
d9 1
a9 1
  This manual set is organized into several parts:
d13 1
a13 1
    <term>Tutorial</term>
d16 1
a16 1
      An informal introduction for new users
d22 1
a22 1
    <term>User's Guide</term>
d25 3
a27 2
      Documents the SQL query language environment, including data types
      and functions.
d33 1
a33 1
    <term>Programmer's Guide</term>
d36 3
a38 3
      Advanced information for application programmers. Topics include
      type and function extensibility, library interfaces,
      and application design issues.
d44 1
a44 1
    <term>Administrator's Guide</term>
d47 3
a49 1
      Installation and server management information
d55 1
a55 1
    <term>Reference Manual</term>
d58 3
a60 1
      Reference pages for SQL command syntax and client and server programs
d66 1
a66 1
    <term>Developer's Guide</term>
d69 5
a73 5
      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>.
d89 2
a90 2
      The <citetitle>Reference Manual</citetitle>'s pages in the traditional
      Unix man format.
@


1.14
log
@Deprecate 'current' for date/time input.
Fix up references to "PostgreSQL" rather than "Postgres". Was roughly
 evenly split between the two before. ref/ files not yet done.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.13 2001/11/08 23:37:50 petere Exp $
d140 1
a140 1
      <productname>PostgreSQL</productname> is an open source effort.
d147 1
a147 1
      features to the code, contribute it.
@


1.13
log
@Small tuning
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.12 2001/09/02 23:27:49 petere Exp $
d130 2
a131 1
      Lounge</ulink> section of the PostgreSQL web site for details.
@


1.12
log
@New blood and fresh air for tutorial
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.11 2001/02/03 19:03:26 petere Exp $
d64 1
a64 1
      Information for <productname>Postgres</productname> developers.
d66 2
a67 2
      <productname>Postgres</productname> project;
      application development information should appear in the 
d77 1
a77 1
  <productname>Postgres</productname> installation and use:
d126 3
a128 4
      The <email>pgsql-general@@postgresql.org</email> (<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 <ulink
d152 2
a153 3
      to start.  The <email>pgsql-docs@@postgresql.org</email> (<ulink
      url="http://www.postgresql.org/mhonarc/pgsql-docs/">archive</ulink>)
      mailing list is the place to get going.
@


1.11
log
@Update, polish, consistencify preface/intro sections.
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.10 2000/12/22 21:51:57 petere Exp $
d16 1
a16 1
      An introduction for new users. Does not cover advanced features.
@


1.10
log
@Make use of <email> tag for marking up email addresses.
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.9 2000/09/29 20:21:34 petere Exp $
d6 1
a6 1
 <title>Resources</title>
d10 63
a74 64
 <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>

d78 82
a160 83

 <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="http://www.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
     <email>pgsql-general@@postgresql.org</email>
     (<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 
     <email>pgsql-docs@@postgresql.org</email>
     (<ulink url="http://www.postgresql.org/mhonarc/pgsql-docs/">archive</ulink>)
     mailing list is the place to get going.
    </para>
   </listitem>
  </varlistentry>
 </variablelist>

@


1.9
log
@Add `id' attributes to all `chapter' and `sect1' tags, to generate useful
names for the HTML files (e.g., not x4856.htm).
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.8 2000/05/11 17:32:32 momjian Exp $
d128 1
a128 1
     <ulink url="mailto:pgsql-general@@postgresql.org">pgsql-general</ulink>
d155 2
a156 2
     <ulink url="mailto:pgsql-docs@@postgresql.org">pgsql-docs</ulink>
     (<ulink url="http://www.PostgreSQL.ORG/mhonarc/pgsql-docs/">archive</ulink>)
@


1.8
log
@Update SGML for FETCH and url's.
@
text
@d2 1
a2 1
$Header: /usr/local/cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.7 2000/05/11 15:18:13 thomas Exp $
d5 1
a5 1
<sect1>
@


1.7
log
@Fix url reference with missing fields.
 Reported by Adrian Oboroc <aoboroc@@btr.md>.
@
text
@d2 1
a2 1
$Header: /home/cvs/pgsql/doc/src/sgml/info.sgml,v 1.6 2000/03/31 03:27:40 thomas Exp $
d115 1
a115 1
     <ulink url="http://postgresql.org"><productname>Postgres</productname></ulink>
@


1.6
log
@Minor markup changes. Refer to (".../catalog") in the emacs hints.
@
text
@d2 1
a2 1
$Header$
d115 1
a115 1
     <ulink url="postgresql.org"><productname>Postgres</productname></ulink>
d129 1
a129 1
     (<ulink url="http://www.PostgreSQL.ORG/mhonarc/pgsql-general/">archive</ulink>)
@


1.5
log
@Minor changes to Fred Horsh's updates.
@
text
@d1 4
d167 1
a167 1
mode: sgml
d177 1
a177 1
sgml-local-catalogs:"/usr/lib/sgml/catalog"
@


1.4
log
@The references to mailing lists in the resources page seem outdated.
Patch attached.

Fred Horch
@
text
@d1 2
a2 2
<Sect1>
<Title>Resources</Title>
d4 173
a176 149
<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>
@


1.3
log
@Clean up to ensure tag completion as required by the newest versions
 of Norm's Modular Style Sheets and jade/docbook.
From Vince Vielhaber <vev@@michvhf.com>.
@
text
@d119 4
a122 3
The <ULink url="mailto:questions@@postgresql.org"><ProductName>Postgres</ProductName> Questions</ULink>
mailing list is a good place to have user questions answered. Other mailing lists are available; consult
the web page for details.
d139 5
a143 3
If you add features to the code, contribute it. 
Even those without a lot of experience can provide
corrections and minor changes in the documentation, and that is a good way to start.
d145 1
a145 1
<ULink url="mailto:docs@@postgresql.org"><ProductName>Postgres</ProductName> Documentation</ULink>
@


1.2
log
@Minor editing and markup changes as a result of preparing the Postscript
 documentation for v6.4.
Bigger updates to the installation instructions (install and config).
@
text
@d6 1
d73 1
@


1.1
log
@Clean up pages. Add information for operator precedence.
Split introduction sections into separate files to allow the legal notice
 and notation sections appear in all documents without having the history
 show up everplace too.
Add full list of reserved and non-reserved key words in syntax.sgml.
Add a separate chapter to the admin guide on security.
@
text
@d51 3
a53 1
project; application development information should appear in the Programmer's Guide.
d63 1
a63 2
At the moment, this manual is very sparse, but eventually should contain
information similar to that in the man pages.
@
