From 5dc3723781fbc88bd9144c2c06fa8c0215311f98 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 11 Sep 2007 17:37:30 +0000 Subject: Stamp releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20. Update FAQs for 8.2.5. --- doc/src/FAQ/FAQ.html | 15 ++--- doc/src/FAQ/FAQ_DEV.html | 152 ++++++++++++++++++++++++------------------ doc/src/FAQ/FAQ_japanese.html | 25 ++++--- 3 files changed, 109 insertions(+), 83 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index f3871873f77..debee4a81fd 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -10,7 +10,7 @@ alink="#0000ff">

Frequently Asked Questions (FAQ) for PostgreSQL

-

Last updated: Wed Apr 18 23:05:05 EDT 2007

+

Last updated: Tue Sep 11 13:34:02 EDT 2007

Current maintainer: Bruce Momjian (bruce@momjian.us) @@ -221,7 +221,7 @@

1.6) What is the most recent release?

-

The latest release of PostgreSQL is version 8.2.4.

+

The latest release of PostgreSQL is version 8.2.5.

We plan to have a major release every year, with minor releases every few months.

@@ -585,8 +585,11 @@

3.6) What is the upgrade process for PostgreSQL?

See http://www.postgresql.org/support/versioning. -

+ href="http://www.postgresql.org/support/versioning">http://www.postgresql.org/support/versioning + for a general discussion about upgrading, and + http://www.postgresql.org/docs/current/static/install-upgrading.html + for specific instructions.

3.7) What computer hardware should I use?

@@ -823,10 +826,6 @@ table?unlimited case to be stored in the column, use a CHECK constraint or a trigger.

- 4.9) In a query, how do I detect if a field - is NULL? How do I concatenate possible NULLs? - How can I sort on whether a field is NULL or not?
-

4.9) In a query, how do I detect if a field is NULL? How do I concatenate possible NULLs? How can I sort on whether a field is NULL or not?

diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index 43ff0c8447f..f14e99f07a1 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -13,7 +13,7 @@

Developer's Frequently Asked Questions (FAQ) for PostgreSQL

-

Last updated: Mon Mar 19 12:52:30 EDT 2007

+

Last updated: Wed Aug 22 20:10:01 EDT 2007

Current maintainer: Bruce Momjian (bruce@momjian.us)
@@ -34,28 +34,29 @@ 1.3) What areas need work?
1.4) What do I do after choosing an item to work on?
- 1.5) I've developed a patch, what next?
- 1.6) Where can I learn more about the code?
- 1.7) How do I download/update the current + 1.5) I have developed a patch, what next?
+ 1.6) How is a patch reviewed?
+ 1.7) Where can I learn more about the code?
+ 1.8) How do I download/update the current source tree?
- 1.8) How do I test my changes?
- 1.9) What tools are available for + 1.9) How do I test my changes?
+ 1.10) What tools are available for developers?
- 1.10) What books are good for developers?
- 1.11) What is configure all about?
- 1.12) How do I add a new port?
- 1.13) Why don't you use threads, raw + 1.11) What books are good for developers?
+ 1.12) What is configure all about?
+ 1.13) How do I add a new port?
+ 1.14) Why don't you use threads, raw devices, async-I/O, <insert your favorite wizz-bang feature here>?
- 1.14) How are RPM's packaged?
- 1.15) How are CVS branches handled?
- 1.16) Where can I get a copy of the SQL + 1.15) How are RPM's packaged?
+ 1.16) How are CVS branches handled?
+ 1.17) Where can I get a copy of the SQL standards?
- 1.17) Where can I get technical + 1.18) Where can I get technical assistance?
- 1.18) How do I get involved in PostgreSQL web + 1.19) How do I get involved in PostgreSQL web site development?
- 1.19) Why haven't you replaced CVS with SVN, Git, + 1.20) Why haven't you replaced CVS with SVN, Git, Monotone, VSS, <insert your favorite SCM system here>? @@ -85,7 +86,7 @@ development?

Download the code and have a look around. See 1.7.

+ "#item1.8">1.8.

Subscribe to and read the pgsql-hackers @@ -137,7 +138,7 @@

You can learn more about these features by consulting the archives, the SQL standards and the recommend texts (see 1.10).

+ "#item1.11">1.11).

1.4) What do I do after choosing an item to work on?

@@ -161,7 +162,7 @@ http://momjian.postgresql.org/cgi-bin/pgpatches_hold.

-

1.5) I've developed a patch, what next?

+

1.5) I have developed a patch, what next?

You will need to submit the patch to pgsql-patches@postgresql.org. It will be reviewed by other contributors to the project and will be @@ -172,7 +173,7 @@

  1. Ensure that your patch is generated against the most recent version of the code, which for developers is CVS HEAD. For more on branches in - PostgreSQL, see 1.15.
    2. + PostgreSQL, see 1.16.
  2. Try to make your patch as readable as possible by following the project's code-layout conventions. This makes it easier for the @@ -203,11 +204,12 @@
  3. New feature patches should also be accompanied by documentation patches. If you need help checking the SQL standard, see 1.16.
    4. + "#item1.17">1.17.
  4. Provide an implementation overview, preferably in code comments. Following the surrounding code commenting style is usually a good - approach.
    5. + approach (also see http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=dgr-FClnxw01linuxcodetips).
  5. If it is a performance patch, please provide confirming test results to show the benefit of your patch. It is OK to post patches @@ -223,7 +225,28 @@

    You will be notified via email when the patch is applied, and your name will appear in the next version of the release notes.

    -

    1.6) Where can I learn more about the +

    1.6) How is a patch reviewed?

    + +

    Patch committers check several things before applying a patch:

    + +
      +
    • Patch follows the SQL standard or community agreed-upon behavior
      • +
    • Style merges seamlessly into the surrounding code
      • +
    • Written as simply and efficiently as possible
      • +
    • Uses the available PostgreSQL subsystems properly
      • +
    • Contains sufficient comments
      • +
    • Contains code that works on all supported operating systems
      • +
    • Has proper documentation
      • +
    • Passes all regression tests, and if needed, adds new ones
      • +
    • Behaves as expected, even under unusual cirumstances
      • +
    • Contains no reliability risks
      • +
    • Does not overly complicate the source code
      • +
    • If performance-related, has a measureable performance benefit
      • +
    • Is of sufficient usefulness to the average PostgreSQL user
      • +
    • Follows existing PostgreSQL coding standards
      • +
    + +

    1.7) Where can I learn more about the code?

    Other than documentation in the source tree itself, you can find @@ -233,7 +256,7 @@ is at http://neilconway.org/talks/hacking/

    -

    1.7) How do I download/update the current +

    1.8) How do I download/update the current source tree?

    There are several ways to obtain the source tree. Occasional @@ -248,7 +271,7 @@ "http://developer.postgresql.org/docs/postgres/cvs.html"> http://developer.postgresql.org/docs/postgres/cvs.html.

    -

    1.8) How do I test my changes?

    +

    1.9) How do I test my changes?

    Basic system testing

    @@ -296,7 +319,7 @@ you can use the --enable-depend option of configure to have the compiler compute the dependencies automatically.

    -

    1.9) What tools are available for +

    1.10) What tools are available for developers?

    First, all the files in the src/tools directory are @@ -402,21 +425,21 @@ There is also a script called unused_oids in pgsql/src/include/catalog that shows the unused oids.

    -

    1.10) What books are good for +

    1.11) What books are good for developers?

    -

    I have four good books, An Introduction to Database - Systems, by C.J. Date, Addison, Wesley, A Guide to the SQL - Standard, by C.J. Date, et. al, Addison, Wesley, - Fundamentals of Database Systems, by Elmasri and Navathe, - and Transaction Processing, by Jim Gray, Morgan, - Kaufmann

    +

    There are five good books: -

    There is also a database performance site, with a handbook - on-line written by Jim Gray at http://www.benchmarkresources.com..

    +
      +
    • An Introduction to Database Systems, by C.J. Date, Addison, Wesley
      • +
    • A Guide to the SQL Standard, by C.J. Date, et. al, Addison, Wesley
      • +
    • Fundamentals of Database Systems, by Elmasri and Navathe
      • +
    • Transaction Processing, by Jim Gray, Morgan, Kaufmann
      • +
    • Transactional Information Systems by Gerhard Weikum, Kaufmann
      • +
    -

    1.11) What is configure all about?

    +

    1.12) What is configure all about?

    The files configure and configure.in are part of the GNU autoconf package. Configure allows us to test for @@ -440,7 +463,7 @@ all files derived by configure are removed, so you see only the file contained in the source distribution.

    -

    1.12) How do I add a new port?

    +

    1.13) How do I add a new port?

    There are a variety of places that need to be modified to add a new port. First, start in the src/template directory. Add an @@ -459,7 +482,7 @@ handling. There is a backend/port directory if you need special files for your OS.

    -

    1.13) Why don't you use threads, raw +

    1.14) Why don't you use threads, raw devices, async-I/O, <insert your favorite wizz-bang feature here>?

    @@ -493,7 +516,7 @@ cautious about their adoption. The TODO list often contains links to discussions showing our reasoning in these areas.

    -

    1.14) How are RPMs packaged?

    +

    1.15) How are RPMs packaged?

    This was written by Lamar Owen and Devrim G端nd端z:

    @@ -578,7 +601,7 @@

    As to why all these files aren't part of the source tree, well, unless there was a large cry for it to happen, we don't believe it should.

    -

    1.15) How are CVS branches managed?

    +

    1.16) How are CVS branches managed?

    This was written by Tom Lane:

    @@ -648,7 +671,7 @@ dot-release or two, so that we won't have to double-patch the first wave of fixes.

    -

    1.16) Where can I get a copy of the SQL +

    1.17) Where can I get a copy of the SQL standards?

    There are three versions of the SQL standard: SQL-92, SQL:1999, @@ -685,7 +708,7 @@ (paper)

    6. -

    1.17) Where can I get technical +

    1.18) Where can I get technical assistance?

    Many technical questions held by those new to the code have been @@ -700,7 +723,7 @@ questions about development of new features, on IRC at irc.freenode.net in the #postgresql channel.

    -

    1.18) How do I get involved in PostgreSQL +

    1.19) How do I get involved in PostgreSQL web site development?

    PostgreSQL website development is discussed on the @@ -710,7 +733,7 @@ , the code for the next version of the website is under the "portal" module.

    -

    1.19) Why haven't you replaced CVS with SVN, Git, +

    1.20) Why haven't you replaced CVS with SVN, Git, Monotone, VSS, <insert your favorite SCMS here>?

    Currently the core developers see no SCMS that will provide @@ -841,24 +864,25 @@

    lfirst(i), lfirst_int(i), lfirst_oid(i)
    -
    return the data (a point, integer and OID respectively) at - list element i.
    +
    return the data (a pointer, integer or OID respectively) of + list cell i.
    lnext(i)
    -
    return the next list element after i.
    +
    return the next list cell after i.
    foreach(i, list)
    - loop through list, assigning each list element to - i. It is important to note that i is a List *, + loop through list, assigning each list cell to + i. It is important to note that i is a ListCell *, not the data in the List element. You need to use lfirst(i) to get at the data. Here is a typical code snippet that loops through a List containing Var *'s and processes each one: 
    - List                *list;
+
+    List        *list;
     ListCell    *i;
 
     foreach(i, list)
@@ -878,26 +902,26 @@
 
         
    lappend(list, node)
    
 
-        
    add node to the end of list. This is more
-        expensive that lcons.
    
+        
    add node to the end of list.
    
 
-        
    nconc(list1, list2)
    
+        
    list_concat(list1, list2)
    
 
-        
    Concat list2 on to the end of list1.
    
+        
    Concatenate list2 on to the end of list1.
    
 
-        
    length(list)
    
+        
    list_length(list)
    
 
         
    return the length of the list.
    
 
-        
    nth(i, list)
    
+        
    list_nth(list, i)
    
 
-        
    return the i'th element in list.
    
+        
    return the i'th element in list,
+         counting from zero.
    
 
-        
    lconsi, ...
    
+        
    lcons_int, ...
    
 
-        
    There are integer versions of these: lconsi,
-        lappendi, etc. Also versions for OID lists: lconso,
-        lappendo, etc.
    
+        
    There are integer versions of these: lcons_int,
+        lappend_int, etc. Also versions for OID lists: lcons_oid,
+        lappend_oid, etc.
    You can print nodes easily inside gdb. First, to disable @@ -922,14 +946,14 @@

    2.4) I just added a field to a structure. What else should I do?

    -

    The structures passing around from the parser, rewrite, +

    The structures passed around in the parser, rewriter, optimizer, and executor require quite a bit of support. Most structures have support routines in src/backend/nodes used to create, copy, read, and output those structures (in particular, the files copyfuncs.c and equalfuncs.c. Make sure you add support for your new field to these files. Find any other places the structure might need code for your new field. mkid - is helpful with this (see 1.9).

    + is helpful with this (see 1.10).

    2.5) Why do we use palloc() and pfree() to allocate memory?

    diff --git a/doc/src/FAQ/FAQ_japanese.html b/doc/src/FAQ/FAQ_japanese.html index a64c4b643ba..f518ca1b0f3 100644 --- a/doc/src/FAQ/FAQ_japanese.html +++ b/doc/src/FAQ/FAQ_japanese.html @@ -9,7 +9,7 @@

    PostgreSQL(ポストグレス・キュー・エル)についてよくある質問とその解答(FAQ)

    -

    原文最終更新日: Tue Mar 20 13:43:40 EDT 2007

    +

    原文最終更新日: Last updated: Tue Apr 24 17:29:38 EDT 2007

    現在の維持管理者: Bruce Momjian (bruce@momjian.us)
    Maintainer of Japanese Translation: Jun Kuwamura (juk at PostgreSQL.jp)

    1.6) 最新のリリースはどれですか？

    -

    PostgreSQL の最新版はバージョン 8.2.3 です。

    +

    PostgreSQL の最新版はバージョン 8.2.4 です。

    我々は、1年毎にメジャーリリースを、数ヵ月ごとのマイナーリリースを 行なうことを計画しています。

    @@ -704,8 +704,12 @@ http://www.postgresql.jp/PostgreSQL/references.html

    3.6) PostgreSQLのアップグレードの手順はどうなりますか？

    -

    バージョン番号付けの方針については、http://www.postgresql.org/support/versioning +

    バージョン番号付けの方針について、更新全般についての解説は + http://www.postgresql.org/support/versioning を、 + そして、詳細についての説明は + http://www.postgresql.org/docs/current/static/install-upgrading.html をご覧ください。

    @@ -740,9 +744,9 @@ http://www.postgresql.jp/PostgreSQL/references.html れは間違いです。ECC RAM、SCSI、および、高品質マザーボードは、安いハー ドウェアに比べると、より信頼性が高く、より性能も良いのです。 PostgreSQL はほとんどのハードウェアで稼働しますが、信頼性や性能が重 - 要な場合は、ハードウェアのオプションを研究することが賢明です。メーリ - ングリストでもハードウェアオプションとトレードオフについて議論するこ - とができます。

    + 要な場合は、使用中のハードウェアのオプションについて調査することが + 賢明です。我々のメーリングリスト上でもハードウェアオプションのトレー + ドオフについて議論することができます。

    @@ -1289,13 +1293,13 @@ http://www.postgresql.jp/PostgreSQL/references.html [訳注： 日本語版の製作については以下の通りです。 - 最終更新日: 2007年03月25日 + 最終更新日: 2007年04月25日 翻訳者: 桑村 潤 (Jun Kuwamura <juk at PostgreSQL.jp>) このFAQの和訳の作成にあたり協力をしてくださった方々(敬称は略させていただきます): 田仲 稔(Minoru TANAKA <Tanaka.Minoru at keiken.co.jp>) - 石井 達夫(Tatsuo ISHII <t-ishii at sra.co.jp>) + 石井 達夫(Tatsuo ISHII <ishii at sraoss.co.jp>) 齊藤 知人(Tomohito SAITOH <tomos at elelab.nsc.co.jp>) 馬場 肇(Hajime BABA <baba at kusastro.kyoto-u.ac.jp>) 岡本 一幸(Kazuyuki OKAMOTO <kaz-okamoto at hitachi-system.co.jp>) @@ -1309,7 +1313,6 @@ http://www.postgresql.jp/PostgreSQL/references.html 神谷 英孝(Hidetaka KAMIYA <hkamiya at catvmics.ne.jp>) 菅原 敦(Atsushi SUGAWARA <asugawar at f3.dion.ne.jp>) 稲葉 香理(Kaori Inaba <i-kaori at sra.co.jp>) - 石井 達夫(Tatsuo Ishii <t-ishii at sra.co.jp>) をはじめ、ポストグレスに関する話題豊富な日本語PostgreSQLメーリングリスト、 和訳のきっかけを作ってくれたり、いつもチェックをしてくれる @@ -1325,7 +1328,7 @@ http://www.postgresql.jp/PostgreSQL/references.html http://www.PostgreSQL.jp/wg/jpugdoc/ 「JPUG文書・書籍関連分科会」 http://www.linux.or.jp/JF/JFdocs/INDEX-database.html 「Linux JFプロジェクト」 - http://www.rccm.co.jp/~juk/pgsql/ 「PostgreSQL Notes for Japanese」（翻訳者ページ） + http://www.linet.gr.jp/~juk/pgsql/ 「PostgreSQL Notes for Japanese」（翻訳者ページ） なお、この和訳に関するご意見・ご質問は(juk at PostgreSQL.jp)までお寄せください。 -- cgit v1.2.3