1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
5
>Further Information</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
12
TITLE="PostgreSQL 9.1beta1 Documentation"
13
HREF="index.html"><LINK
16
HREF="preface.html"><LINK
19
HREF="notation.html"><LINK
21
TITLE="Bug Reporting Guidelines"
22
HREF="bug-reporting.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2011-04-27T21:20:33"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.1beta1 Documentation</A
89
TITLE="Bug Reporting Guidelines"
90
HREF="bug-reporting.html"
105
>Further Information</A
108
> Besides the documentation, that is, this book, there are other
109
resources about <SPAN
127
HREF="http://wiki.postgresql.org"
130
> contains the project's <A
131
HREF="http://wiki.postgresql.org/wiki/Frequently_Asked_Questions"
135
(Frequently Asked Questions) list, <A
136
HREF="http://wiki.postgresql.org/wiki/Todo"
140
detailed information about many more topics.
152
HREF="http://www.postgresql.org"
156
carries details on the latest release and other
157
information to make your work or play with
168
> The mailing lists are a good place to have your questions
169
answered, to share experiences with other users, and to contact
170
the developers. Consult the <SPAN
184
> is an open-source project.
185
As such, it depends on the user community for ongoing support.
186
As you begin to use <SPAN
190
will rely on others for help, either through the documentation
191
or through the mailing lists. Consider contributing your
192
knowledge back. Read the mailing lists and answer questions. If
193
you learn something which is not in the documentation, write it
194
up and contribute it. If you add features to the code,
208
SUMMARY="Footer navigation table"
237
HREF="bug-reporting.html"
261
>Bug Reporting Guidelines</TD
b'\\ No newline at end of file'