Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 78EC7475AE4 for ; Sun, 20 Oct 2002 14:25:42 -0400 (EDT) Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65]) by postgresql.org (Postfix) with ESMTP id 30FBC4758BD for ; Sun, 20 Oct 2002 14:25:41 -0400 (EDT) Received: from ianb.local (pD9517091.dip.t-dialin.net [217.81.112.145]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id UAA10807; Sun, 20 Oct 2002 20:25:20 +0200 (MET DST) From: Ian Barwick To: Bruce Momjian Subject: "Cosmetic" FAQ patch Date: Sun, 20 Oct 2002 20:26:54 +0200 X-Mailer: KMail [version 1.4] Cc: pgsql-docs@postgresql.org MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_UWLAV5GUO1179K8I63LZ" Message-Id: <200210202026.54423.barwick@gmx.net> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/14 X-Sequence-Number: 1508 --------------Boundary-00=_UWLAV5GUO1179K8I63LZ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable A few very minor changes (also making the document=20 correct HTML 4.01 transitional as defined by=20 validator.w3.org, FWIW ;-). German FAQ will follow in a day or two. Ian Barwick barwick@gmx.net --------------Boundary-00=_UWLAV5GUO1179K8I63LZ Content-Type: text/x-diff; charset="us-ascii"; name="FAQ.html.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="FAQ.html.patch" Index: FAQ.html =================================================================== RCS file: /projects/cvsroot/pgsql-server/doc/src/FAQ/FAQ.html,v retrieving revision 1.161 diff -c -r1.161 FAQ.html *** FAQ.html 2002/10/17 23:34:10 1.161 --- FAQ.html 2002/10/20 18:16:28 *************** *** 1,12 **** ! ! - - - ! PostgreSQL FAQ --- 1,8 ---- ! ! PostgreSQL FAQ *************** *** 80,89 **** clients" when trying to connect?
3.9) What is in the pgsql_tmp directory?
! 3.10) Why do I need to do a dump and restore to upgrade PostgreSQL releases?
-

Operational Questions

4.1) What is the difference between binary cursors and normal cursors?
--- 76,85 ---- clients" when trying to connect?
3.9) What is in the pgsql_tmp directory?
! 3.10) Why do I need to do a dump and restore to upgrade PostgreSQL releases?
+

Operational Questions

4.1) What is the difference between binary cursors and normal cursors?
*************** *** 440,448 **** Features section above. We are built for reliability and features, though we continue to improve performance in every release. There is an interesting Web page comparing PostgreSQL to ! MySQL at ! ! http://openacs.org/why-not-mysql.html

--- 436,443 ---- Features section above. We are built for reliability and features, though we continue to improve performance in every release. There is an interesting Web page comparing PostgreSQL to ! MySQL at ! http://openacs.org/philosophy/why-not-mysql.html

*************** *** 653,659 ****

If you are doing many INSERTs, consider doing them in a large batch using the COPY command. This ! is much faster than individual INSERTS. Second, statements not in a BEGIN WORK/COMMIT transaction block are considered to be in their own transaction. Consider performing several statements in a single transaction block. This --- 648,654 ----

If you are doing many INSERTs, consider doing them in a large batch using the COPY command. This ! is much faster than individual INSERTS. Second, statements not in a BEGIN WORK/COMMIT transaction block are considered to be in their own transaction. Consider performing several statements in a single transaction block. This *************** *** 721,727 ****

If postmaster is running, start psql in one window, then find the PID of the postgres process used by psql. Use a debugger to attach to the ! postgres PID. You can set breakpoints in the debugger and issue queries from psql. If you are debugging postgres startup, you can set PGOPTIONS="-W n", then start psql. This will cause startup to delay for n seconds --- 716,722 ----

If postmaster is running, start psql in one window, then find the PID of the postgres process used by psql. Use a debugger to attach to the ! postgres PID. You can set breakpoints in the debugger and issue queries from psql. If you are debugging postgres startup, you can set PGOPTIONS="-W n", then start psql. This will cause startup to delay for n seconds *************** *** 759,765 **** maximum number of processes, NPROC; the maximum number of processes per user, MAXUPRC; and the maximum number of open files, NFILE and ! NINODE. The reason that PostgreSQL has a limit on the number of allowed backend processes is so your system won't run out of resources.

--- 754,760 ---- maximum number of processes, NPROC; the maximum number of processes per user, MAXUPRC; and the maximum number of open files, NFILE and ! NINODE. The reason that PostgreSQL has a limit on the number of allowed backend processes is so your system won't run out of resources.

*************** *** 768,781 **** the MaxBackendId constant in include/storage/sinvaladt.h.

!

3.9) What are the pgsql_tmp ! directory?

!

They are temporary files generated by the query executor. For ! example, if a sort needs to be done to satisfy an ORDER ! BY, and the sort requires more space than the backend's ! -S parameter allows, then temporary files are created to ! hold the extra data.

The temporary files are usually deleted automatically, but might remain if a backend crashes during a sort. A stop and restart of the --- 763,775 ---- the MaxBackendId constant in include/storage/sinvaladt.h.

!

3.9) What is in the pgsql_tmp directory?

!

This directory contains temporary files generated by the query ! executor. For example, if a sort needs to be done to satisfy an ! ORDER BY and the sort requires more space than the ! backend's -S parameter allows, then temporary files are created ! here to hold the extra data.

The temporary files are usually deleted automatically, but might remain if a backend crashes during a sort. A stop and restart of the *************** *** 815,821 ****

The entire query may have to be evaluated, even if you only want the first few rows. Consider using a query that has an ORDER ! BY. If there is an index that matches the ORDER BY, PostgreSQL may be able to evaluate only the first few records requested, or the entire query may have to be evaluated until the desired rows have been generated.

--- 809,815 ----

The entire query may have to be evaluated, even if you only want the first few rows. Consider using a query that has an ORDER ! BY. If there is an index that matches the ORDER BY, PostgreSQL may be able to evaluate only the first few records requested, or the entire query may have to be evaluated until the desired rows have been generated.

*************** *** 955,976 ****

When using wild-card operators such as LIKE or ! ~, indexes can only be used in certain circumstances:

  • The beginning of the search string must be anchored to the start ! of the string, i.e.:
      • !
    • LIKE patterns must not start with %.
    • ~ (regular expression) patterns must start with ! ^.
      • !
  • The search string can not start with a character class, e.g. [a-e].
  • Case-insensitive searches such as ILIKE and ~* do not utilise indexes. Instead, use functional indexes, which are described in section 4.12.
  • The default C locale must be used during ! initdb.

--- 949,970 ----

When using wild-card operators such as LIKE or ! ~, indexes can only be used in certain circumstances:

  • The beginning of the search string must be anchored to the start ! of the string, i.e.
      !
    • LIKE patterns must not start with %.
    • ~ (regular expression) patterns must start with ! ^.
      • !
  • The search string can not start with a character class, e.g. [a-e].
  • Case-insensitive searches such as ILIKE and ~* do not utilise indexes. Instead, use functional indexes, which are described in section 4.12.
  • The default C locale must be used during ! initdb.

*************** *** 1341,1347 **** Because PostgreSQL loads database-specific system catalogs, it is uncertain how a cross-database query should even behave.

!

/contrib/dblink allows cross-database queries using function calls. Of course, a client can make simultaneous connections to different databases and merge the results on the client side.

--- 1335,1341 ---- Because PostgreSQL loads database-specific system catalogs, it is uncertain how a cross-database query should even behave.

!

contrib/dblink allows cross-database queries using function calls. Of course, a client can make simultaneous connections to different databases and merge the results on the client side.

*************** *** 1378,1390 ****

4.28) What encryption options are available?

    !
  • /contrib/pgcrypto contains many encryption functions for use in SQL queries.
  • The only way to encrypt transmission from the client to the server is by using hostssl in pg_hba.conf.
  • Database user passwords are automatically encrypted when stored in version 7.3. In previous versions, you must enable the option ! PASSWORD_ENCRYPTION in postgresql.conf.
  • The server can run using an encrypted file system.
--- 1372,1384 ----

4.28) What encryption options are available?

    !
  • contrib/pgcrypto contains many encryption functions for use in SQL queries.
  • The only way to encrypt transmission from the client to the server is by using hostssl in pg_hba.conf.
  • Database user passwords are automatically encrypted when stored in version 7.3. In previous versions, you must enable the option ! PASSWORD_ENCRYPTION in postgresql.conf.
  • The server can run using an encrypted file system.
*************** *** 1412,1418 **** functions are fully supported in C, PL/PgSQL, and SQL. See the Programmer's Guide for more information. An example of a table-returning function defined in C can be found in ! contrib/tablefunc.

5.4) I have changed a source file. Why does the recompile not see the change?

--- 1406,1412 ---- functions are fully supported in C, PL/PgSQL, and SQL. See the Programmer's Guide for more information. An example of a table-returning function defined in C can be found in ! contrib/tablefunc.

5.4) I have changed a source file. Why does the recompile not see the change?

--------------Boundary-00=_UWLAV5GUO1179K8I63LZ--