From jd@commandprompt.com Fri Jul 14 17:10:59 2006 X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 24F1E9F95E3; Fri, 14 Jul 2006 14:10:59 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 45963-05; Fri, 14 Jul 2006 14:10:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from projects.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 221C49FAC76; Fri, 14 Jul 2006 14:10:41 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by projects.commandprompt.com (8.13.6/8.13.6) with ESMTP id k6EHAcnY011086; Fri, 14 Jul 2006 10:10:38 -0700 Message-ID: <44B7D011.4020307@commandprompt.com> Date: Fri, 14 Jul 2006 10:10:41 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.4 (X11/20060615) MIME-Version: 1.0 To: "Joshua D. Drake" CC: Robert Treat , pgsql-docs@postgresql.org, PostgreSQL-patches Subject: Maintenance and External Projects (try 2) References: <44B6EC25.7000708@commandprompt.com> <200607140757.31021.xzilla@users.sourceforge.net> <44B7B61D.6010806@commandprompt.com> In-Reply-To: <44B7B61D.6010806@commandprompt.com> Content-Type: multipart/mixed; boundary="------------060703040407000407040508" X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (projects.commandprompt.com [192.168.2.159]); Fri, 14 Jul 2006 10:10:43 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/5 X-Sequence-Number: 3595 This is a multi-part message in MIME format. --------------060703040407000407040508 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello, I did further work on both of these. Cleaned up some stupid spelling and typos (forgot an s here, a y there ;)). The commit log doesn't change from previous except that I added a reference to Sourceforge for external projects, and I specified that there are three required routing maintenance tasks. Please let me know if there is anything else you would like me to do or add. Joshua D. Drake -- === 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/ --------------060703040407000407040508 Content-Type: text/x-patch; name="external-projects.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="external-projects.patch" *** external-projects.sgml 2006-07-14 09:35:39.820149250 -0700 --- external-projects.sgml.diff 2006-07-14 09:33:42.864840000 -0700 *************** *** 1,29 **** ! External Projects PostgreSQL is a complex software project, and managing it is difficult. We have found that many enhancements to PostgreSQL can be more ! 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. ! Many PostgreSQL-related projects are ! hosted at either ! GBorg ! or pgFoundry. ! There are other PostgreSQL-related projects that are hosted ! elsewhere, but you will have to do an Internet search to find them. --- 1,34 ---- ! PgFoundry and External Projects PostgreSQL is a complex software project, and managing it is difficult. We have found that many enhancements to PostgreSQL can be more ! efficiently developed separately from the core project. ! ! ! ! To help our community with the development of their external projects ! we have created PgFoundry. ! Pgfoundry utlizes the Gforge ! 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 management ! resources such as mailing lists, forums and cvs please feel free to create ! a new project. ! Secondly, many PostgreSQL-related projects are ! still hosted at GBorg. ! Gborg is the original external community developer site. It is currently deprecated ! in favor of PgFoundry but still contains many active and relevant projects. There ! are other popular PostgreSQL related projects that are ! hosted independently as well as at other community sites such as ! SourceForge. You should you google if you ! don't find the project you are looking for. *************** *** 36,46 **** PostgreSQL includes very few interfaces with the base distribution. libpq is packaged because ! it is the primary C interface and many other ! interfaces are built on top of it. ecpg is packaged ! because it is tied to the server-side grammar so is very dependent ! on the database version. All the other interfaces are independent ! projects and must be installed separately. --- 41,50 ---- PostgreSQL includes very few interfaces with the base distribution. libpq is packaged because ! it is the primary dependecy of most interfaces available to PostgreSQL. ! We also package ecpg is because it is tied to the ! server-side grammar. All other interfaces, such as PHP, Perl, Python, ! and Ruby are external projects. *************** *** 52,115 **** This is the most common interface for Windows ! applications. ! pgjdbc ! A JDBC interface. ! Npgsql ! ! ! .Net interface for more recent ! Windows applications. ! ! ! ! ! ! libpqxx ! A newer C++ interface. ! libpq++ ! An older C++ interface. ! pgperl ! A Perl interface with an API similar ! to libpq. ! DBD-Pg ! A Perl interface that uses the ! DBD-standard API. --- 56,113 ---- This is the most common interface for Windows ! applications. Website. ! ODBCng ! Another ODBC driver for PostgreSQL. ! Website. ! pgjdbc ! A JDBC interface. ! Website. ! Npgsql ! .Net interface for more recent ! mono/C# applications. ! Website. ! libpqxx ! A newer C++ interface. ! Website. ! DBD::Pg ! A Perl DBI driver for PostgreSQL. ! Website. *************** *** 119,151 **** A newer version of the Tcl interface. ! pgtcl ! The original version of the Tcl interface. - - - PyGreSQL - - - A Python interface library. - - - - - - All of these can be found at - GBorg - or pgFoundry. --- 117,137 ---- A newer version of the Tcl interface. + Website. ! Pyscopg ! A Python interface library that is DB API 2.0 compliant. ! Website. *************** *** 175,181 **** There are several administration tools available for PostgreSQL. The most popular is ! pgAdmin, and there are several commercially available ones. --- 161,167 ---- There are several administration tools available for PostgreSQL. The most popular is ! pgAdmin, and there are several commercially available ones. --------------060703040407000407040508 Content-Type: text/x-patch; name="maintenance.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="maintenance.patch" *** maintenance.sgml 2006-07-14 09:35:40.180171750 -0700 --- maintenance.diff 2006-07-14 10:06:13.642756000 -0700 *************** *** 7,48 **** maintenance ! There are a few routine maintenance chores that must be performed on ! a regular basis to keep a PostgreSQL ! server running smoothly. The tasks discussed here are repetitive ! in nature and can easily be automated using standard Unix tools such ! as cron scripts. But it is the database ! administrator's responsibility to set up appropriate scripts, and to ! check that they execute successfully. ! ! One obvious maintenance task is creation of backup copies of the data on a ! regular schedule. Without a recent backup, you have no chance of recovery ! after a catastrophe (disk failure, fire, mistakenly dropping a critical ! table, etc.). The backup and recovery mechanisms available in ! PostgreSQL are discussed at length in ! . ! The other main category of maintenance task is periodic vacuuming ! of the database. This activity is discussed in ! . ! Something else that might need periodic attention is log file management. This is discussed in . ! ! PostgreSQL is low-maintenance compared ! 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. ! Routine Vacuuming --- 7,46 ---- maintenance + + Routine maintenance + + ! PostgreSQL, like any database software requires that certain tasks ! be performed regularly to achieve optimum performance. The tasks ! discussed here are required but they ! are repetitive in nature and can easily be automated using standard ! Unix tools such as cron scripts. ! ! PostgreSQL is low-maintenance compared ! to other database management systems. It is also fairly easy, provided ! you read the documentation. ! There are three tasks that must be performed on ! a periodic basis. The first is backups. If you do not have a current backup ! and your system experiences a catostrophic failure, you will loose your data. ! You can read further about backups procedures in . ! The second is vacuum which is discussed in . ! The third is to update the planner statistics using the analyze command as ! discussed in . ! Another task that may need periodic attention is log file management. This is discussed in . ! Routine Vacuuming *************** *** 53,63 **** PostgreSQL's VACUUM command ! must be run on a regular basis for several reasons: ! To recover disk space occupied by updated or deleted rows. --- 51,61 ---- PostgreSQL's VACUUM command ! must be run on a regular basis for several reasons: ! To recover or reuse disk space occupied by updated or deleted rows. *************** *** 82,92 **** ! The standard form of VACUUM can run in parallel with ! normal database operations (SELECTs, INSERTs, UPDATEs, DELETEs, but not ! changes to table definitions). ! Beginning in PostgreSQL 8.0, there are ! configuration parameters that can be adjusted to further reduce the performance impact of background vacuuming. See . --- 80,91 ---- ! The standard form of 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 PostgreSQL 8.0, introduced new ! configuration parameters to further reduce the potentially negative performance impact of background vacuuming. See . --------------060703040407000407040508-- From tgl@sss.pgh.pa.us Fri Jul 14 18:38:02 2006 X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D77209FAD5A for ; Fri, 14 Jul 2006 15:38:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 34882-01 for ; Fri, 14 Jul 2006 15:37:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 98D1F9FAE4E for ; Fri, 14 Jul 2006 15:37:58 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6EIbuqZ003366; Fri, 14 Jul 2006 14:37:57 -0400 (EDT) To: "Joshua D. Drake" cc: Robert Treat , pgsql-docs@postgresql.org, PostgreSQL-patches Subject: Re: Maintenance and External Projects (try 2) In-reply-to: <44B7D011.4020307@commandprompt.com> References: <44B6EC25.7000708@commandprompt.com> <200607140757.31021.xzilla@users.sourceforge.net> <44B7B61D.6010806@commandprompt.com> <44B7D011.4020307@commandprompt.com> Comments: In-reply-to "Joshua D. Drake" message dated "Fri, 14 Jul 2006 10:10:41 -0700" Date: Fri, 14 Jul 2006 14:37:56 -0400 Message-ID: <3365.1152902276@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/6 X-Sequence-Number: 3596 "Joshua D. Drake" writes: > Please let me know if there is anything else you would like me to do or add. A round of copy-editing seems indicated, at least. regards, tom lane From jd@commandprompt.com Fri Jul 14 19:23:22 2006 X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 4C5F39FAD5A; Fri, 14 Jul 2006 16:23:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 42614-05; Fri, 14 Jul 2006 16:23:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from projects.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 25CE99FAC76; Fri, 14 Jul 2006 16:23:16 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by projects.commandprompt.com (8.13.6/8.13.6) with ESMTP id k6EJNIXj014444; Fri, 14 Jul 2006 12:23:18 -0700 Message-ID: <44B7EF29.5080302@commandprompt.com> Date: Fri, 14 Jul 2006 12:23:21 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.4 (X11/20060615) MIME-Version: 1.0 To: Tom Lane CC: Robert Treat , pgsql-docs@postgresql.org, PostgreSQL-patches Subject: Re: Maintenance and External Projects (try 2) References: <44B6EC25.7000708@commandprompt.com> <200607140757.31021.xzilla@users.sourceforge.net> <44B7B61D.6010806@commandprompt.com> <44B7D011.4020307@commandprompt.com> <3365.1152902276@sss.pgh.pa.us> In-Reply-To: <3365.1152902276@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (projects.commandprompt.com [192.168.2.159]); Fri, 14 Jul 2006 12:23:19 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/7 X-Sequence-Number: 3597 Tom Lane wrote: > "Joshua D. Drake" writes: >> Please let me know if there is anything else you would like me to do or add. > > A round of copy-editing seems indicated, at least. Oh, no doubt. I tried to fix as much as I find, including a bunch of stuff already there. However, I do not claim, in any way to be an editor. Sincerely, Joshua D. Drake > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > -- === 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/ From xzilla@users.sourceforge.net Sat Jul 15 04:04:34 2006 X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 633669FB40E; Sat, 15 Jul 2006 01:04:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 16408-04; Sat, 15 Jul 2006 04:04:24 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from eastrmmtao01.cox.net (eastrmmtao01.cox.net [68.230.240.38]) by postgresql.org (Postfix) with ESMTP id 902BF9FB6DA; Fri, 14 Jul 2006 23:26:04 -0300 (ADT) Received: from [192.168.0.9] (really [24.250.222.197]) by eastrmmtao01.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060715022602.TPQY12077.eastrmmtao01.cox.net@[192.168.0.9]>; Fri, 14 Jul 2006 22:26:02 -0400 From: Robert Treat To: "Joshua D. Drake" Subject: Re: Maintenance and External Projects (try 2) Date: Fri, 14 Jul 2006 22:26:00 -0400 User-Agent: KMail/1.9.1 Cc: Tom Lane , pgsql-docs@postgresql.org, PostgreSQL-patches References: <44B6EC25.7000708@commandprompt.com> <3365.1152902276@sss.pgh.pa.us> <44B7EF29.5080302@commandprompt.com> In-Reply-To: <44B7EF29.5080302@commandprompt.com> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_4IFuEAO6N3+eaC2" Message-Id: <200607142226.00900.xzilla@users.sourceforge.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/8 X-Sequence-Number: 3598 --Boundary-00=_4IFuEAO6N3+eaC2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Friday 14 July 2006 15:23, Joshua D. Drake wrote: > Tom Lane wrote: > > "Joshua D. Drake" writes: > >> Please let me know if there is anything else you would like me to do or > >> add. > > > > A round of copy-editing seems indicated, at least. > > Oh, no doubt. I tried to fix as much as I find, including a bunch of > stuff already there. However, I do not claim, in any way to be an editor. > The following patches provide some editorializing for Joshua's patches. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL --Boundary-00=_4IFuEAO6N3+eaC2 Content-Type: text/x-diff; charset="iso-8859-1"; name="rht.external-projects.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rht.external-projects.patch" Index: doc/src/sgml/external-projects.sgml =================================================================== RCS file: /projects/cvsroot/pgsql/doc/src/sgml/external-projects.sgml,v retrieving revision 1.10 diff -c -r1.10 external-projects.sgml *** doc/src/sgml/external-projects.sgml 10 Mar 2006 19:10:47 -0000 1.10 --- doc/src/sgml/external-projects.sgml 15 Jul 2006 02:22:02 -0000 *************** *** 1,29 **** ! External Projects PostgreSQL is a complex software project, ! and managing it is difficult. We have found that many enhancements to PostgreSQL can be more ! 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. ! Many PostgreSQL-related projects are ! hosted at either ! GBorg ! or pgFoundry. ! There are other PostgreSQL-related projects that are hosted ! elsewhere, but you will have to do an Internet search to find them. --- 1,34 ---- ! PgFoundry and External Projects PostgreSQL is a complex software project, ! and managing the project is difficult. We have found that many enhancements to PostgreSQL can be more ! efficiently developed separately from the core project. ! ! ! ! To help our community with the development of their external projects, ! we have created the PgFoundry. ! PgFoundry is built using the ! GForge software project and is similar to SourceForge in its feature set. If ! you have a PostgreSQL related Open Source project that you would like to ! develop and need project management resources such as mailing lists, forums, ! bug tracking, and CVS, please feel free to create a new project. ! Secondly, many PostgreSQL-related projects are ! still hosted at GBorg. ! GBorg is the original external community developer site, and while it is ! currently closed to new projects in favor of PgFoundry, it still contains ! many active and relevant projects. There are other popular PostgreSQL ! related projects that are hosted independently as well at other community ! sites such as SourceForge. You should ! google if you don't find the project you are looking for. *************** *** 36,46 **** PostgreSQL includes very few interfaces with the base distribution. libpq is packaged because ! it is the primary C interface and many other ! interfaces are built on top of it. ecpg is packaged ! because it is tied to the server-side grammar so is very dependent ! on the database version. All the other interfaces are independent ! projects and must be installed separately. --- 41,50 ---- PostgreSQL includes very few interfaces with the base distribution. libpq is packaged because ! it is the primary dependecy of most interfaces available to PostgreSQL. ! We also package ecpg because it is tied to the ! server-side grammar. All other interfaces, such as PHP, Perl, Python, ! and Ruby, are external projects. *************** *** 52,115 **** This is the most common interface for Windows ! applications. ! ! ! ! ! ! pgjdbc ! ! ! A JDBC interface. ! Npgsql ! .Net interface for more recent ! Windows applications. ! libpqxx ! A newer C++ interface. ! libpq++ ! An older C++ interface. ! pgperl ! A Perl interface with an API similar ! to libpq. ! DBD-Pg ! A Perl interface that uses the ! DBD-standard API. --- 56,112 ---- This is the most common interface for Windows ! applications. Website. ! ODBCng ! Another ODBC driver for PostgreSQL. ! Website. ! pgjdbc ! A JDBC interface. ! Website. ! Npgsql ! .Net interface for more recent mono/C# applications. ! Website. ! libpqxx ! A newer C++ interface. ! Website. ! DBD::Pg ! A Perl DBI driver for PostgreSQL. ! Website. *************** *** 119,151 **** A newer version of the Tcl interface. ! pgtcl ! ! ! The original version of the Tcl interface. ! ! ! ! ! ! PyGreSQL ! A Python interface library. - - - All of these can be found at - GBorg - or pgFoundry. --- 116,136 ---- A newer version of the Tcl interface. + Website. ! Pyscopg ! A Python interface library that is DB API 2.0 compliant. ! Website. *************** *** 175,182 **** There are several administration tools available for PostgreSQL. The most popular is ! pgAdmin, and there are several commercially ! available ones. --- 160,167 ---- There are several administration tools available for PostgreSQL. The most popular is ! pgAdmin III, ! and there are several commercially available ones as well. --Boundary-00=_4IFuEAO6N3+eaC2 Content-Type: text/x-diff; charset="iso-8859-1"; name="rht.maintenance.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rht.maintenance.patch" Index: doc/src/sgml/maintenance.sgml =================================================================== RCS file: /projects/cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v retrieving revision 1.56 diff -c -r1.56 maintenance.sgml *** doc/src/sgml/maintenance.sgml 18 Jun 2006 15:38:35 -0000 1.56 --- doc/src/sgml/maintenance.sgml 15 Jul 2006 02:21:25 -0000 *************** *** 7,48 **** maintenance ! There are a few routine maintenance chores that must be performed on ! a regular basis to keep a PostgreSQL ! server running smoothly. The tasks discussed here are repetitive ! in nature and can easily be automated using standard Unix tools such ! as cron scripts. But it is the database ! administrator's responsibility to set up appropriate scripts, and to ! check that they execute successfully. ! ! One obvious maintenance task is creation of backup copies of the data on a ! regular schedule. Without a recent backup, you have no chance of recovery ! after a catastrophe (disk failure, fire, mistakenly dropping a critical ! table, etc.). The backup and recovery mechanisms available in ! PostgreSQL are discussed at length in ! . ! The other main category of maintenance task is periodic vacuuming ! of the database. This activity is discussed in ! . ! Something else that might need periodic attention is log file management. This is discussed in . ! ! PostgreSQL is low-maintenance compared ! 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. ! Routine Vacuuming --- 7,46 ---- maintenance + + Routine maintenance + + ! PostgreSQL, like any database software, requires that certain tasks ! be performed regularly to achieve optimum performance. The tasks ! discussed here are required, but they ! are repetitive in nature and can easily be automated using standard ! Unix tools such as cron scripts. ! ! PostgreSQL is low-maintenance compared ! to other database management systems. It is also fairly easy, provided ! you read the documentation. ! There are three tasks that must be performed on ! a periodic basis. The first is backups. If you do not have a current backup ! and your system experiences a catastrophic failure, you will lose your data. ! You can read further about backups procedures in . ! The second is vacuum which is discussed in . ! The third is to update the planner statistics using the analyze command as ! discussed in . ! Another task that may need periodic attention is log file management. This is discussed in . ! Routine Vacuuming *************** *** 53,63 **** PostgreSQL's VACUUM command ! must be run on a regular basis for several reasons: ! To recover disk space occupied by updated or deleted rows. --- 51,61 ---- PostgreSQL's VACUUM command ! must be run on a regular basis for several reasons: ! To recover or reuse disk space occupied by updated or deleted rows. *************** *** 82,92 **** ! The standard form of VACUUM can run in parallel with ! normal database operations (SELECTs, INSERTs, UPDATEs, DELETEs, but not ! changes to table definitions). ! Beginning in PostgreSQL 8.0, there are ! configuration parameters that can be adjusted to further reduce the performance impact of background vacuuming. See . --- 80,91 ---- ! The standard form of VACUUM does not intefere with production ! database operations. Items such as SELECTS, INSERTS, UPDATES and DELETES ! will continue to function as normal, though you will not be able to modify the ! definition (Such as ALTER TABLE ADD COLUMN) of a table while it is being vacuumed. ! The release of PostgreSQL 8.0, introduced new ! configuration parameters to further reduce the potentially negative performance impact of background vacuuming. See . *************** *** 187,195 **** ! If you have a table whose contents are deleted on a periodic ! basis, consider doing it with TRUNCATE rather ! than using DELETE followed by VACUUM. TRUNCATE removes the entire content of the table immediately, without requiring a subsequent VACUUM or VACUUM --- 186,194 ---- ! If you have a table whose entire contents are deleted on a periodic ! basis, consider doing it with the TRUNCATE rather ! than using the DELETE followed by VACUUM. TRUNCATE removes the entire content of the table immediately, without requiring a subsequent VACUUM or VACUUM --Boundary-00=_4IFuEAO6N3+eaC2-- From bruce@momjian.us Sat Jul 29 17:36:54 2006 X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5BD089FB2C6; Sat, 29 Jul 2006 14:36:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 83491-02-7; Sat, 29 Jul 2006 14:36:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 413459FB2D1; Sat, 29 Jul 2006 14:36:34 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id k6THaR304876; Sat, 29 Jul 2006 13:36:27 -0400 (EDT) From: Bruce Momjian Message-Id: <200607291736.k6THaR304876@momjian.us> Subject: Re: Maintenance and External Projects (try 2) In-Reply-To: <200607142226.00900.xzilla@users.sourceforge.net> To: Robert Treat Date: Sat, 29 Jul 2006 13:36:27 -0400 (EDT) CC: "Joshua D. Drake" , Tom Lane , pgsql-docs@postgresql.org, PostgreSQL-patches X-Mailer: ELM [version 2.4ME+ PL122k (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.039 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200607/23 X-Sequence-Number: 3613 Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches It will be applied as soon as one of the PostgreSQL committers reviews and approves it. --------------------------------------------------------------------------- Robert Treat wrote: > On Friday 14 July 2006 15:23, Joshua D. Drake wrote: > > Tom Lane wrote: > > > "Joshua D. Drake" writes: > > >> Please let me know if there is anything else you would like me to do or > > >> add. > > > > > > A round of copy-editing seems indicated, at least. > > > > Oh, no doubt. I tried to fix as much as I find, including a bunch of > > stuff already there. However, I do not claim, in any way to be an editor. > > > > The following patches provide some editorializing for Joshua's patches. > > -- > Robert Treat > Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL [ Attachment, skipping... ] [ Attachment, skipping... ] > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + From bruce@momjian.us Tue Aug 1 00:10:31 2006 X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id B95B59FB309; Mon, 31 Jul 2006 21:10:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 17869-06; Tue, 1 Aug 2006 00:10:10 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 0CDAC9FB2BE; Mon, 31 Jul 2006 21:10:08 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id k710A7F19239; Mon, 31 Jul 2006 20:10:07 -0400 (EDT) From: Bruce Momjian Message-Id: <200608010010.k710A7F19239@momjian.us> Subject: Re: Maintenance and External Projects (try 2) In-Reply-To: <200607142226.00900.xzilla@users.sourceforge.net> To: Robert Treat Date: Mon, 31 Jul 2006 20:10:07 -0400 (EDT) CC: "Joshua D. Drake" , Tom Lane , pgsql-docs@postgresql.org, PostgreSQL-patches X-Mailer: ELM [version 2.4ME+ PL122k (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.816 tagged_above=0 required=5 tests=SPF_HELO_SOFTFAIL, SPF_SOFTFAIL X-Spam-Level: *** X-Archive-Number: 200607/26 X-Sequence-Number: 3616 Patch applied. Thanks. --------------------------------------------------------------------------- Robert Treat wrote: > On Friday 14 July 2006 15:23, Joshua D. Drake wrote: > > Tom Lane wrote: > > > "Joshua D. Drake" writes: > > >> Please let me know if there is anything else you would like me to do or > > >> add. > > > > > > A round of copy-editing seems indicated, at least. > > > > Oh, no doubt. I tried to fix as much as I find, including a bunch of > > stuff already there. However, I do not claim, in any way to be an editor. > > > > The following patches provide some editorializing for Joshua's patches. > > -- > Robert Treat > Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL [ Attachment, skipping... ] [ Attachment, skipping... ] > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +