Hello,
Updated to have stronger wording for vacuuming. Cleaned out some extra
superlatives. Added a couple of index entries for Routine Maintenance
and added entry specific to Analyze.
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
? external_projects.diff
? maintenance.diff
Index: external-projects.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/external-projects.sgml,v
retrieving revision 1.10
diff -r1.10 external-projects.sgml
4c4
< <title>External Projects</title>
---
> <title>PgFoundry and External Projects</title>
10,17c10,20
< efficiently developed separately from the core project. Separate
< projects can
< have their own developer teams, email lists, bug tracking,
< and release schedules. While their independence makes
< development easier, it makes users' jobs harder. They have to hunt
< around looking for database enhancements to meet their needs.
< This section describes some of the more popular externally
< developed enhancements and guides you on how to find them.
---
> efficiently developed separately from the core project. To help our
> community with the development process of their external projects
> we have created <ulink url="http://www.pgfoundry.org/">PgFoundry</ulink>.
> </para>
>
> <para>
> <ulink url="http://www.pgfoundry.org/">Pgfoundry</ulink> utlizes the Gforg
> software and is similar to SourceForge in its feature set. If you have an
> Open Source project that you would like to develop and need project
> mangement
> resources including, mailing lists, forums and cvs please feel free to
> create
> a new project.
21,26c24,29
< Many <productname>PostgreSQL</productname>-related projects are
< hosted at either
< <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>
< or <ulink url="http://pgfoundry.org"><productname>pgFoundry</></ulink>.
< There are other <productname>PostgreSQL</productname>-related projects
that are hosted
< elsewhere, but you will have to do an Internet search to find them.
---
> Secondly, many <productname>PostgreSQL</productname>-related projects are
> hosted at either <ulink
> url="http://pgfoundry.org"><productname>pgFoundry</></ulink>
> or <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>
> (although
> Gbord is considered deprecated). There are other
> <productname>PostgreSQL</productname>
> noteable related projects that are hosted elsewhere. However, you will
> also want to
> do an Internet search to find others.
55c58
< applications.
---
> applications. <ulink url="http://odbc.postgresql.org/">Website.</ulink>
61c64
< <term>pgjdbc</term>
---
> <term>ODBCng</term>
64c67,68
< A <application>JDBC</> interface.
---
> Another ODBC driver for PostgreSQL.
> <ulink
> url="http://projects.commandprompt.com/public/odbcng/">Website.</ulink>
70,80c74
< <term>Npgsql</term>
< <listitem>
< <para>
< <application>.Net</> interface for more recent
< <application>Windows</> applications.
< </para>
< </listitem>
< </varlistentry>
<
< <varlistentry>
< <term>libpqxx</term>
---
> <term>pgjdbc</term>
83c77,78
< A newer <application>C++</> interface.
---
> A <application>JDBC</> interface.
> <ulink url="http://jdbc.postgresql.org/">Website.</ulink>
89c84
< <term>libpq++</term>
---
> <term>Npgsql</term>
92c87,89
< An older <application>C++</> interface.
---
> <application>.Net</> interface for more recent
> <application>mono/C#</> applications.
> <ulink url="http://pgfoundry.org/projects/npgsql/">Website.</ulink>
98c95
< <term>pgperl</term>
---
> <term>libpqxx</term>
101,102c98,99
< A <application>Perl</> interface with an <acronym>API</> similar
< to <application>libpq</>.
---
> A newer <application>C++</> interface.
> <ulink
> url="http://thaiopensource.org/development/libpqxx/">Website.</ulink>
108c105
< <term>DBD-Pg</term>
---
> <term>DBD::Pg</term>
111,112c108,109
< A <application>Perl</> interface that uses the
< <acronym>DBD</>-standard <application>API</>.
---
> A <application>Perl</> DBI driver for PostgreSQL.
> <ulink url="http://search.cpan.org/dist/DBD-Pg/">Website.</ulink>
121a119
> <ulink
> url="http://gborg.postgresql.org/project/pgtclng/projdisplay.php">Website.</ulink>
127c125
< <term>pgtcl</term>
---
> <term>Pyscopg</term>
130c128
< The original version of the <application>Tcl</> interface.
---
> A <application>Python</> interface librar that is DB API 2.0 compliant.
134,143d131
<
< <varlistentry>
< <term>PyGreSQL</term>
< <listitem>
< <para>
< A <application>Python</> interface library.
< </para>
< </listitem>
< </varlistentry>
<
145,148d132
<
< All of these can be found at
< <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>
< or <ulink url="http://pgfoundry.org"><productname>pgFoundry</></ulink>.
Index: maintenance.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v
retrieving revision 1.56
diff -r1.56 maintenance.sgml
9a10,13
> <indexterm zone="maintenance">
> <primary>Routine maintenance</primary>
> </indexterm>
>
11,17c15,19
< There are a few routine maintenance chores that must be performed on
< a regular basis to keep a <productname>PostgreSQL</productname>
< server running smoothly. The tasks discussed here are repetitive
< in nature and can easily be automated using standard Unix tools such
< as <application>cron</application> scripts. But it is the database
< administrator's responsibility to set up appropriate scripts, and to
< check that they execute successfully.
---
> PostgreSQL, like any database software requires that tasks
> be performed on a regular basis to achieve optimum performance.
> The tasks discussed here are <emphasis>required</emphasis> but they
> are repetitive in nature and can easily be automated using standard
> Unix tools such as <application>cron</application> scripts.
30,32c32,36
< The other main category of maintenance task is periodic <quote>vacuuming</>
< of the database. This activity is discussed in
< <xref linkend="routine-vacuuming">.
---
> The are two tasks that <emphasis>must</emphasis> be performed on
> a periodic basis. The first is vacuuming. This activity is discussed in
> <xref linkend="routine-vacuuming">. The sceond is to update the planner
> statistics using the analyze command as discussed in
> <xref linkend="vacuum-for-statistics">.
42,44c46,48
< to some other database management systems. Nonetheless,
< appropriate attention to these tasks will go far towards ensuring a
< pleasant and productive experience with the system.
---
> to other database management systems. It is also fairly easy, provided
> you read the documentation to keep a relatively hands off maintenance
> regimen.
56c60
< must be run on a regular basis for several reasons:
---
> <emphasis>must</emphasis> be run on a regular basis for several reasons:
60c64
< <simpara>To recover disk space occupied by updated or deleted
---
> <simpara>To recover or reuse disk space occupied by updated or deleted
85,89c89,94
< The standard form of <command>VACUUM</> can run in parallel with
< normal database operations (SELECTs, INSERTs, UPDATEs, DELETEs, but not
< changes to table definitions).
< Beginning in <productname>PostgreSQL</productname> 8.0, there are
< configuration parameters that can be adjusted to further reduce the
---
> The standard form of <command>VACUUM</> does not intefere with production
> database operations. Items such as SELECTS, INSERTS, UPDATES and DELETES
> will continue to function as normal. You will not be able to modify the
> definition (Such as ALTER TABLE ADD COLUMN) of a table.
> The release of <productname>PostgreSQL</productname> 8.0, introduced new
> configuration parameters to further reduce the potentially negative
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq