From 2e964aee757c1000590fc38c411ebdfbd66d37fe Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 11 Mar 2005 21:47:44 +0000 Subject: Here's the patch to fix a lot of markup errors in the HTML FAQs. Doesn't change content (at least not supposed to). Magnus Hagander --- doc/src/FAQ/FAQ.html | 36 +++-- doc/src/FAQ/FAQ_DEV.html | 31 ++-- doc/src/FAQ/FAQ_MINGW.html | 2 - doc/src/FAQ/FAQ_brazilian.html | 42 ++--- doc/src/FAQ/FAQ_czech.html | 38 ++--- doc/src/FAQ/FAQ_french.html | 13 +- doc/src/FAQ/FAQ_german.html | 18 +-- doc/src/FAQ/FAQ_japanese.html | 345 ++++++++++++++++++++++------------------- doc/src/FAQ/FAQ_polish.html | 54 +++---- doc/src/FAQ/FAQ_russian.html | 31 ++-- doc/src/FAQ/FAQ_turkish.html | 20 +-- 11 files changed, 326 insertions(+), 304 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index d328aa639a5..32ed55ac000 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: Thu Feb 24 19:33:07 EST 2005
Last updated: Fri Mar 11 16:42:06 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -113,8 +113,9 @@ databases?
4.19) How do I return multiple rows or columns from a function?
- 4.20) Why do I get "missing oid" errors when - accessing temporary tables in PL/PgSQL functions?
+ 4.20) Why do I get "relation with OID ##### + does not exist" errors when accessing temporary tables in PL/PgSQL + functions?
4.21) What encryption options are available?
@@ -196,7 +197,7 @@ and Win2003. A prepackaged installer is available at http://pgfoundry.org/projects/pginstaller. MSDOS-based versions - of Windows (Win95, Win98, WinMe) can run PostgreSQL using Cygwin. + of Windows (Win95, Win98, WinMe) can run PostgreSQL using Cygwin.
There is also a Novell Netware 6 port at http://forge.novell.com, @@ -216,14 +217,14 @@ via email. The main web site to subscribe to the email lists is http://www.postgresql.org/community/lists/. The general - or bugs lists are a good place to start. + or bugs lists are a good place to start.
The major IRC channel is #postgresql on Freenode (irc.freenode.net). To connect you can use the Unix program irc -c '#postgresql' "$USER" irc.freenode.net or use any of the other popular IRC clients. A Spanish one also exists on the same network, (#postgresql-es), and a French one, - (#postgresqlfr). There is also a PostgreSQL channel on EFNet. + (#postgresqlfr). There is also a PostgreSQL channel on EFNet.
A list of commercial support companies is available at @@ -412,7 +413,7 @@ href="http://www.php.net">http://www.php.net) is an excellent interface.
For complex cases, many use the Perl DBD::Pg with CGI.pm or +
For complex cases, many use the Perl and DBD::Pg with CGI.pm or mod_perl.
2.3) Does PostgreSQL have a graphical user @@ -481,7 +482,7 @@
Use of Prepared queries
Use of ANALYZE to maintain accurate optimizer statistics
Regular use of VACUUM or pg_autovacuum +
Regular use of VACUUM or pg_autovacuum
Dropping of indexes during large data changes
@@ -608,7 +609,7 @@ SELECT time, use a cursor and FETCH.
To SELECT a random row, use: +
To SELECT a random row, use:
     SELECT col
     FROM tab
@@ -642,7 +643,7 @@
     4.3) How do you change a column's data type?
 
     Changing the data type of a column can be done easily in 8.0
-    and later with ALTER TABLE ALTER COLUMN TYPE.
+    and later with ALTER TABLE ALTER COLUMN TYPE.
 
     In earlier releases, do this:
 @@ -660,7 +661,7 @@
 
     These are the limits:
 
-
+
@@ -730,7 +731,7 @@ table?
     used if the table is larger than a minimum size, and the query
     selects only a small percentage of the rows in the table. This is
     because the random disk access caused by an index scan can be
-    slower than a straight read through the table, or sequential scan. 
+    slower than a straight read through the table, or sequential scan. 
To determine if an index should be used, PostgreSQL must have
     statistics about the table. These statistics are collected using
@@ -842,7 +843,7 @@ table?
4.10) What is the difference between the
     various character types?

-

 Maximum size for a database? unlimited (32 TB databases
 exist)
 Maximum size for a table? 32 TB
unlimited
 
     unlimited
     
 
+
@@ -1056,10 +1057,11 @@ lengthIt is easy using set-returning functions, 
     
-    http://techdocs.postgresql.org/guides/SetReturningFunctions.
+    http://techdocs.postgresql.org/guides/SetReturningFunctions.
 
-    4.20) Why do I get "missing oid" errors when
-    accessing temporary tables in PL/PgSQL functions?
+    4.20) Why do I get "relation with OID #####
+    does not exist" errors when accessing temporary tables in PL/PgSQL
+    functions?
PL/PgSQL caches function scripts, and an unfortunate side effect
     is that if a PL/PgSQL function accesses a temporary table, and that
@@ -1080,7 +1082,7 @@ length
     pg_hba.conf, and the client sslmode must not be
     disable. (Note that it is also possible to use a third-party
     encrypted transport, such as stunnel or ssh, rather than PostgreSQL's
-    native SSL connections.)
+    native SSL connections.)
     
Database user passwords are automatically encrypted when stored in
     the system tables.
The server can run using an encrypted file system.
diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
index c43dc78af49..76872983670 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: Wed Jan  5 17:36:58 EST 2005
+    Last updated: Fri Mar 11 16:43:05 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)

@@ -26,9 +26,7 @@
     

      
 
-    

       General Questions
-    1.1) How do I get involved in PostgreSQL
     development?
1.2) What development environment is required
@@ -59,9 +57,7 @@
     site development?

      
 
-    
       Technical Questions
-    2.1) How do I efficiently access information in
     tables from the backend code?
2.2) Why are table, column, type, function,
@@ -83,7 +79,7 @@
       General Questions
 
-    1.1) How go I get involved in PostgreSQL
+    
1.1) How do I get involved in PostgreSQL
     development?
Download the code and have a look around. See 
 
+    
A web site is maintained for patches that are ready to be applied,
+    
+    http://momjian.postgresql.org/cgi-bin/pgpatches, and
+    those that are being kept for the next release,
+    
+    http://momjian.postgresql.org/cgi-bin/pgpatches2.
+    
     1.5) Where can I learn more about the
     code?
 
@@ -192,7 +195,7 @@
     Basic system testing
The easiest way to test your code is to ensure that it builds
-    against the latest verion of the code and that it does not generate
+    against the latest version of the code and that it does not generate
     compiler warnings.
It is worth advised that you pass --enable-cassert to
@@ -210,7 +213,7 @@
     directory of the source tree. If any tests failure,
     investigate.
 
-    If you've deliberately changed existing behaviour, this change
+    
If you've deliberately changed existing behavior, this change
     may cause a regression test failure but not any actual regression.
     If so, you should also patch the regression test suite.
 
@@ -472,7 +475,7 @@
 
       The initscript;
 
-      Any other ancilliary scripts and files;
+      Any other ancillary scripts and files;
A README.rpm-dist document that tries to adequately document
       both the differences between the RPM build and the WHY of the
@@ -601,7 +604,7 @@
     cvs ... checkout pgsql
 
 
-    To get a past branch, you cd to whereever you want it and
+    
To get a past branch, you cd to wherever you want it and
     say
      cvs ... checkout -r BRANCHNAME pgsql
@@ -682,7 +685,7 @@
     questions about development of new features, on IRC at
     irc.freenode.net in the #postgresql channel.
 
-    1.18) How go I get involved in PostgreSQL
+    
1.18) How do I get involved in PostgreSQL
     web site development?
 
     PostgreSQL website development is discussed on the
@@ -690,15 +693,13 @@
     the source code is available at http://gborg.postgresql.org/project/pgweb/projdisplay.php
     , the code for the next version of the website is under the
-    "portal" module. You will al so find code for the "techdocs"
+    "portal" module. You will also find code for the "techdocs"
     website if you would like to contribute to that. A temporary todo
     list for current website development issues is available at http://xzilla.postgresql.org/todo
 
-    
       Technical Questions
-    
 
     2.1) How do I efficiently access information
     in tables from the backend code?
@@ -810,7 +811,7 @@
       
         lfirst(i), lfirst_int(i), lfirst_oid(i)
 
-        return the data (a point, inteter and OID respectively) at
+        
return the data (a point, integer and OID respectively) at
         list element i.
 
         lnext(i)
diff --git a/doc/src/FAQ/FAQ_MINGW.html b/doc/src/FAQ/FAQ_MINGW.html
index 924d20ef4d8..2f8bfc4ced6 100644
--- a/doc/src/FAQ/FAQ_MINGW.html
+++ b/doc/src/FAQ/FAQ_MINGW.html
@@ -71,8 +71,6 @@ The mailing list for discussion is
 pgsql-hackers-win32@postgresql.org. You can subscribe by sending
 an email body containing the word subscribe to pgsql-hackers-win32-request@postgresql.org.

-
-
 Resources
 There are several resources that helped us complete this port:

 
diff --git a/doc/src/FAQ/FAQ_brazilian.html b/doc/src/FAQ/FAQ_brazilian.html
index a07ffbdf9c1..ad123d5bee9 100644
--- a/doc/src/FAQ/FAQ_brazilian.html
+++ b/doc/src/FAQ/FAQ_brazilian.html
@@ -17,7 +17,7 @@
     
 
     Traduzido por: Euler Taveira de Oliveira (eulerto@yahoo.com.br)

+    "mailto:eulerto@yahoo.com.br">eulerto@yahoo.com.br)
 
     A versão mais recente desse documento pode ser vista em 
@@ -202,14 +202,14 @@
     baseados no NT tais como Win2000, WinXP e Win2003. Um instalador
     está disponível em 
-	    http://pgfoundry.org/projects/pginstaller Versões do Windows
-    baseados no MSDOS (Win95, Win98, WinMe) podem executar o PostgreSQL utilizando o Cygwin.
+	    http://pgfoundry.org/projects/pginstaller Versões do Windows
+    baseados no MSDOS (Win95, Win98, WinMe) podem executar o PostgreSQL utilizando o Cygwin.
 
     Há também um porte para Novell Netware 6 em
     http://forge.novell.com
-    e uma versão para OS/2 (eComStation) em 
-    http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F.
+    e uma versão para OS/2 (eComStation) em 
+    http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F.
 
     1.5) Onde eu posso conseguir o PostgreSQL?
 
@@ -253,7 +253,7 @@ Há também uma lista de discussão dos desenvolvedores dispon
 Outras listas de discussões e informações sobre o PostgreSQL podem ser encontradas na homepage do PostgreSQL em:
 
     
-      http://www.PostgreSQL.org
+      http://www.PostgreSQL.org
     
 
     O principal canal de IRC é o #postgresql na Freenode (irc.freenode.net). Para se conectar você pode utilizar o comando Unix irc -c '#postgresql' "$USER" irc.freenode.net ou utilizar qualquer outro cliente de IRC. Um canal hispânico (#postgresql-es) e um francês (#postgresqlfr) também existem na mesma rede. Há também um canal PostgreSQL na EFNet.
@@ -499,9 +499,9 @@ Há também uma lista de discussão dos desenvolvedores dispon
 
 Se o postmaster não está sendo executado, você pode executar o núcleo do postgres a partir da linha de comando, e digitar a sua sentença SQL diretamente. Isso é recomendado somente para fins de depuração. Note que uma nova linha termina a consulta, e não um ponto-e-vírgula. Se você compilou com símbolos de depuração, você pode utilizar um depurador para ver o que está acontecendo. Como o núcleo (backend) não foi iniciado a partir do postmaster, ele não está executando em um ambiente idêntico e problemas de iteração com o núcleo/travamento não podem ser reproduzidos.
 
-Se o postmaster está sendo executado, inicie o psql em uma janela, e então encontre o PID do processo postgres utilizado pelo psql utilizando 
SELECT pg_backend_pid()
. Utilize um depurador para anexar ao PID do postgres. Você pode definir pontos de parada (breakpoints) no depurador e digitar consultas no psql. Se você está depurando a inicialização do postgres, você pode definir PGOPTIONS="-W n" e então iniciar o psql. Isto retardará a inicialização por n segundos então você pode anexar o depurador ao processo, definir quaisquer pontos de parada e continuar pela sequência de inicialização.
+Se o postmaster está sendo executado, inicie o psql em uma janela, e então encontre o PID do processo postgres utilizado pelo psql utilizando SELECT pg_backend_pid(). Utilize um depurador para anexar ao PID do postgres. Você pode definir pontos de parada (breakpoints) no depurador e digitar consultas no psql. Se você está depurando a inicialização do postgres, você pode definir PGOPTIONS="-W n" e então iniciar o psql. Isto retardará a inicialização por n segundos então você pode anexar o depurador ao processo, definir quaisquer pontos de parada e continuar pela sequência de inicialização.
 
-Há várias variáveis de configuração do servidor 
log_*
 que habilitam a exibição de estatísticas que podem ser muito úteis para depuração e medidas de performance.
+Há várias variáveis de configuração do servidor log_* que habilitam a exibição de estatísticas que podem ser muito úteis para depuração e medidas de performance.
 
 Você também pode compilar com perfil para ver que funções estão demandando tempo de execução. Os arquivo de perfil do núcleo (backend) serão colocados no diretório pgsql/data/base/dbname. O arquivo de perfil do cliente será colocado no diretório atual do cliente. O Linux requer uma compilação com -DLINUX_PROFILE para criação dos perfis.
 
@@ -526,7 +526,7 @@ Há também uma lista de discussão dos desenvolvedores dispon
 
     3.11) Que tipo de hardware eu devo usar?
 
-    Por causa do hardware de PC ser em sua maioria compatível, pessoas tendem a acreditar que todos os hardwares de PC são de mesma qualidade. Não é verdade. ECC RAM, SCSI e placas mãe de qualidade são mais confiáveis e têm uma melhor performance do que hardwares mais baratos. O PostgreSQL executará em quase todo hardware, mas se a confiabilidade e a performance forem importantes é prudente pesquisar sobre as opções de hardware. Nossas listas de discussão podem ser usadas para discutir opções de hardware e dilemas.
+    Por causa do hardware de PC ser em sua maioria compatível, pessoas tendem a acreditar que todos os hardwares de PC satilde;o de mesma qualidade. Natilde;o é verdade. ECC RAM, SCSI e placas mãe de qualidade são mais confiáveis e têm uma melhor performance do que hardwares mais baratos. O PostgreSQL executará em quase todo hardware, mas se a confiabilidade e a performance forem importantes é prudente pesquisar sobre as opções de hardware. Nossas listas de discussão podem ser usadas para discutir opções de hardware e dilemas.
 
     
 
@@ -543,7 +543,7 @@ Há também uma lista de discussão dos desenvolvedores dispon
 
     Toda a consulta tem que ser avaliada, mesmo se você só quer os primeiros registros. Considere utilizar uma consulta que tenha um ORDER BY. Se há um índice que combina com o ORDER BY, o PostgreSQL pode ser capaz de avaliar somente os primeiros registros requisitados, ou toda consulta tem que ser avaliada até que os registros desejados tenham sido gerados.
 
-    Para obter um registro randômico, utilize:
+    
Para obter um registro randômico, utilize:
      SELECT col
     FROM tab
@@ -639,7 +639,7 @@ Número máximo de índices em uma tabela?        ilimitado
     utilizados se uma tabela é maior do que o tamanho mínimo e uma consulta
     seleciona somente uma porcentagem pequena de registros de uma tabela. Isto porque
     o acesso randômico ao disco causado por uma busca por índice pode ser
-    mais lento do que uma leitura ao longo da tabela ou uma busca sequencial.
+    mais lento do que uma leitura ao longo da tabela ou uma busca sequencial.
 
     Para determinar se um índice pode ser utilizado, o PostgreSQL deve ter
     estatísticas sobre a tabela. Estas estatísticas são coletadas utilizando
@@ -686,11 +686,10 @@ Número máximo de índices em uma tabela?        ilimitado
     
A localidade padrão C deve ser utilizada durante o
     initdb porque não é possível saber o próximo/maior caracter
     em uma localidade que não seja a C. Você pode criar um índice
-    especial text_pattern_ops para tais casos que funcionam somente para
-    indexação utilizando LIKE.
+    especial text_pattern_ops para tais casos que funcionam somente para
+    indexação utilizando LIKE.
     
     
-    
 
     
Em versões anteriores a 8.0, índices frequentemente não podiam ser usados a menos que os tipos de dados correspodessem aos tipos da coluna do índice. Isto é particularmente verdadeiro para índices de coluna int2, int8 e numeric.
 
@@ -922,14 +921,15 @@ Veja a página sobre create_sequence no manual para mais informa&cc
     FROM tab
     WHERE col IN (SELECT subcol FROM subtab);
 
-    por:
+por:
     SELECT *
     FROM tab
     WHERE EXISTS (SELECT subcol FROM subtab WHERE subcol = col);
 
-
-Para isto ser rápido, subcol deve ser uma coluna indexada. A partir da versão 7.4, IN utiliza a mesma técnica de agrupamento do que consultas normais, e é recomendado utilizar EXISTS.
-
+

+Para isto ser rápido, subcol deve ser uma coluna indexada.
+A partir da versão 7.4, IN utiliza a mesma técnica de agrupamento do que consultas normais, e é recomendado utilizar EXISTS.
+
     4.23) Como eu faço uma junção externa (outer join)?
 
     PostgreSQL suporta junções externas utilizando a sintaxe padrão do SQL. Aqui temos dois exemplos:
@@ -965,7 +965,7 @@ Para isto ser rápido, subcol deve ser uma coluna indexada. <
 
     4.25) Como eu retorno múltiplos registros ou colunas de uma função?
 
-    No 7.3, você pode facilmente retornar múltiplos registros ou colunas de uma função, http://techdocs.postgresql.org/guides/SetReturningFunctions.
+    
No 7.3, você pode facilmente retornar múltiplos registros ou colunas de uma função, http://techdocs.postgresql.org/guides/SetReturningFunctions.
 
     4.26) Por que eu não posso confiar na criação/remoção de tabelas temporárias em funções PL/PgSQL?
     PL/PgSQL armazena o conteúdo da função, e o efeito indesejado é que se uma função PL/PgSQL acessa uma tabela temporária, e aquela tabela é removida e criada novamente, e a função é chamada novamente, a função irá falhar porque o conteúdo armazenado da função ainda apontará para a tabela temporária antiga. A solução é utilizar o EXECUTE para acesso a tabelas temporárias no PL/PgSQL. Isto irá fazer com que a consulta seja avaliada toda vez.
@@ -973,7 +973,7 @@ Para isto ser rápido, subcol deve ser uma coluna indexada. <
     4.27) Que opções para encriptação estão disponíveis?
     
 	    No contrib/pgcrypto contém muitas funções de encriptação para serem utilizados em consultas SQL.
-	    Para encriptar a transmissão do cliente ao servidor, o servidor deve ter a opção ssl definida como true no postgresql.conf, e um registro host ou hostssl deve existir no pg_hba.conf, e o sslmode no cliente não deve estar disable. (Note que também é possível utilizar outros esquemas de transporte encriptado, tais como stunnel ou ssh, ao invés da conexão SSL nativa do PostgreSQL.)
+	    
Para encriptar a transmissão do cliente ao servidor, o servidor deve ter a opção ssl definida como true no postgresql.conf, e um registro host ou hostssl deve existir no pg_hba.conf, e o sslmode no cliente não deve estar disable. (Note que também é possível utilizar outros esquemas de transporte encriptado, tais como stunnel ou ssh, ao invés da conexão SSL nativa do PostgreSQL.)
 	    Senhas dos usuários do banco de dados são automaticamente encriptadas quando armazenadas na versão 7.3. Em versões anteriores, você deve habilitar a opção PASSWORD_ENCRYPTION no postgresql.conf.
 	    O servidor pode executar utilizando um sistema de arquivos encriptado.
     
diff --git a/doc/src/FAQ/FAQ_czech.html b/doc/src/FAQ/FAQ_czech.html
index cb91c8eb90e..05079c79767 100644
--- a/doc/src/FAQ/FAQ_czech.html
+++ b/doc/src/FAQ/FAQ_czech.html
@@ -129,7 +129,7 @@
  
    Obecné otázky
 
-   1.1) Co je PostgreSQL? Jak se vyslovuje?
+   1.1) Co je PostgreSQL? Jak se vyslovuje?
 
    PostgreSQL se vyslovuje Post-Gres-Q-L. Zvukový záznam je 
    dostupný na adrese .
@@ -206,18 +206,18 @@
    Win32 knihovny libpq a psql. K databázi PostgerSQL lze pøistupovat skrze
    rozhraní ODBC.
 
-   Server

+   
Server
 
    Server mù¾e být na WindowsNT a Win2k provozován pouze s knihovnou
    Cygwin, Cygnus Unix/NT porting library. Více pgsql/doc/FAQ_MSWIN v
    distribuci nebo MS Windows FAQ na adrese
-   http://www.PostgreSQL.org/docs/faqs/text/FAQ_MSWIN.
+   http://www.PostgreSQL.org/docs/faqs/text/FAQ_MSWIN.
 
    Na nativním portu pro MS Win NT/2000/XP se pracuje. Dal¹í informace
    o aktuálním stavu PostgreSQL pro Windows naleznet na adrese
    http://techdocs.postgresql.org/guides/Windows a
    
-   http://momjian.postgresql.org/main/writings/pgsql/win32.html.
+   http://momjian.postgresql.org/main/writings/pgsql/win32.html.
 
    Existující port pro Novell Netware 6 naleznete na
    http://forge.novell.com.
@@ -238,7 +238,7 @@
     subscribe
     end
 
-   na adresu 
+na adresu 
    pgsql-general-request@PostgreSQL.org.
 
    Mù¾ete si vy¾ádat denní pøehled (diggest), který má zhruba 30K dennì
@@ -254,7 +254,7 @@
 
    
Seznam dal¹ích konferencí naleznete na stránkách PostgreSQL:
    
-   http://www.postgresql.org
+   http://www.postgresql.org
    
    1.7) Jaká je poslední verze?
 
@@ -315,7 +315,7 @@
 
    Nejdøíve si stáhnìte nejnovìj¹í zdroje a pøeètìte si vývojáøskou
    dokumentaci na na¹em webu nebo v distribuci. Pak se pøihla¹te do
-   konferencí pgsql-hackers a 
pgsql-patches. Kvalitní záplaty posílejte do
+   konferencí pgsql-hackers a pgsql-patches. Kvalitní záplaty posílejte do
    pgsql-patches.
 
    Právo commit má v CVS archivu asi tøinácti lidí. Ka¾dý z nich poslal
@@ -341,7 +341,7 @@
 	DBMS, napø. transakce, vnoøené dotazy, spou¹tì, pohledy, kontrolu 
 	referenèní integrity a sofistikované zamykání. Podporuje nìkteré 
 	vlastnosti, které tyto systémy nemají, u¾ivatelem definované typy, 
-	dìdiènost, pravidla, MVCC redukující zamykání.


+	dìdiènost, pravidla, MVCC redukující zamykání.


 
    
Výkon
 	Výkonnostnì je na tom PostgreSQL podobnì jako dal¹í komerèní ale 
@@ -363,7 +363,7 @@
 	kód s minimem chyb. Ka¾dá verze je více ne¾ mìsíc v beta testování, 
 	a na¹e historie verzí ukazuje, ¾e mù¾eme nabídnout stabilní, solidní 
 	verze, které jsou pøipraveny pro reálné nasazení. V této oblasti 
-	jsme srovnatelní s dal¹ími databázemi.


+	jsme srovnatelní s dal¹ími databázemi.


 
    Podpora
 	Na na¹í mailové konferenci mù¾ete kontaktovat velkou skupinu 
@@ -375,7 +375,7 @@
 	kteøí vy¾adují podporu ke konkrétním pøípadùm, existuje placená 
 	podpora (FAQ sekce 1.6).


 
-   Cena

+   
Cena
 	PosgreSQL lze volnì pou¾ívat pro nekomerèní i komerèní pou¾ití. 
 	Mù¾ete do svých produktù pøidat ná¹ kód bez omezení, respektive 
 	v souladu s podmínkami na¹í licenèní smlouvy (v duchu BSD licence).

@@ -553,7 +553,7 @@
    napøíklad:
      cd /usr/local/pgsql
-    ./bin/postmaster > server.log 2>&1 &
+    ./bin/postmaster > server.log 2>&1 &
 
    Tím se vytvoøí log v adresáøi PostgreSQL, Tento soubor obsahuje u¾iteèné
    informace o problémech a chybách vyskytlých se na serveru. Postmaster má
@@ -773,7 +773,7 @@
 
    
Jinak je tomu v pøípadì pou¾ití LIMIT a ORDER BY, pøi kterém se vìt¹inou
    index pou¾ije, výsledkem je pouze malá èást tabulky. Funkce MAX() a
-   MIN() nepou¾ívají indexy, ale je mo¾né tuté¾ hodnotu získat:
+   MIN() nepou¾ívají indexy, ale je mo¾né tuté¾ hodnotu získat:
      SELECT col 
     FROM tab
@@ -791,7 +791,7 @@
       
         vzor LIKE nesmí zaèínat %
         ~ regulární výraz musí zaèínat ^
-      
+      
vzor nesmí zaèínat intervalem, napø. [a-e]
vyhledávaní, které není Case sensitiv jako je ILIKE nebo ~* 
       nepou¾ívá indexy. Mù¾ete ale pou¾ít funkcionální indexy, které jsou 
@@ -926,7 +926,7 @@ BYTEA       bytea               pole byt
    Koneènì mù¾ete pou¾ít OID hodnotu vrácenou pøíkazem INSERT, ale to je
    pravdìpodobnì nejménì pøenositelné øe¹ení. V Perlu pøi pou¾ití DBI
    modulu Edmunda Mergleho DBD:Pg oid hodnotu získáme $sth->{pg_oid_status}
-   po ka¾dém $sth->execute().
+   po ka¾dém $sth->execute().
 
    4.15.3) Nepovede currval() a nextval() k rozhození 
      podmínek pøi soubìhu s jinými u¾ivateli?
@@ -986,7 +986,7 @@ BYTEA       bytea               pole byt
       
 pøidání, vkládání (append, insert)
 OID, serial value (OID, serial value)
 portal, kurzor (portal, cursor)
-       range variable, jméno tabulky, alias tabulky (range
+       range variable, jméno tabulky, alias tabulky (range
         variable, table name, table alias)
 
@@ -1038,13 +1038,13 @@ CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
    Døívìj¹í verze (pøed 7.4) spojovali vnoøené dotazy k vnìj¹ím sekvenèním
    ètením výsledku poddotazu pro ka¾dý øádek vnìj¹ího dotazu. Pokud poddotaz
    vrátil nìkolik málo øádkù IN bylo rychlé. Pro ostatní pøípady je vhodné
-   nahradit IN EXISTS:
+   nahradit IN EXISTS:
     SELECT * 
     FROM tab
     WHERE col IN (SELECT subcol FROM subtab);
 
-  na:
+na:
    SELECT * 
    FROM tab
@@ -1101,7 +1101,7 @@ CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
 
    V PostgreSQL 7.3 mù¾ete jednodu¹e vracet více øádkù nebo sloupcù z
    funkce, viz:
-   http://techdocs.postgresql.org/guides/SetReturningFunctions.
+   http://techdocs.postgresql.org/guides/SetReturningFunctions.
 
    4.26) Proè nelze spolehlivì vytváøet a ru¹it doèasné tabulky v PL/pgSQL funkcích?
 
@@ -1164,4 +1164,4 @@ CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
    pøepínaè --enable-depend pøíkazu configure k automatickému øe¹ení
    závislostí pøekladaèem.
  
-
\ No newline at end of file
+
diff --git a/doc/src/FAQ/FAQ_french.html b/doc/src/FAQ/FAQ_french.html
index 0436774159b..c48334ea91c 100644
--- a/doc/src/FAQ/FAQ_french.html
+++ b/doc/src/FAQ/FAQ_french.html
@@ -152,7 +152,7 @@
 
     PostgreSQL se prononce Post-Gres-Q-L. Un fichier audio est
     disponible sur http://www.postgresql.org/postgresql.mp3
+    href="http://www.postgresql.org/postgresql.mp3">http://www.postgresql.org/postgresql.mp3
     pour ceux souhaitant entendre la prononciation.
 
     PostgreSQL est une amélioration du système de gestion de bases
@@ -173,7 +173,7 @@
     développement de PostgreSQL. C'est un projet soutenu par une
     communauté sans être contrôlé par une société. Pour y contribuer,
     voir la FAQ des développeurs sur http://www.postgresql.org/docs/faqs/FAQ_DEV.html.
+    href="http://www.postgresql.org/docs/faqs/FAQ_DEV.html">http://www.postgresql.org/docs/faqs/FAQ_DEV.html.
 
     Les auteurs de PostgreSQL 1.01 étaient Andrew Yu et Jolly Chen.
     Beaucoup d'autres personnes ont contribué au portage, aux tests,
@@ -292,7 +292,7 @@
     PostgreSQL sur le site web de PostgreSQL :
 
     
-      http://www.PostgreSQL.org
+      http://www.PostgreSQL.org
     
 
     Il y a aussi un canal IRC sur Freenode et EFNet, le canal
@@ -819,7 +819,7 @@
     l'intégralité de la requête peut être évaluée, jusqu'à générer les lignes
     désirées.
 
-    Pour faire un SELECT sur une ligne aléatoire :
+    
Pour faire un SELECT sur une ligne aléatoire :
      SELECT colonne
     FROM table
@@ -1004,7 +1004,6 @@
     La locale C par défaut doit être utilisée lors de
     initdb.
     
-    
 
     
Dans les versions antérieures à la 8.0, les indexs ne peuvent souvent
     pas être utilisés sauf si les types de données correspondent exactement au
@@ -1398,7 +1397,7 @@ BYTEA           bytea           tableau d'octets (accepte les octets nuls)
     
A partir de la 7.3, vous pouvez facilement renvoyer plusieurs lignes ou
     colonnes à partir d'une fonction,
     
-    http://techdocs.postgresql.org/guides/SetReturningFunctions.
+    http://techdocs.postgresql.org/guides/SetReturningFunctions.
 
     4.26) Pourquoi ne puis-je pas créer/supprimer des
     tables temporaires dans les fonctions PL/PgSQL de façon stable ?
@@ -1422,7 +1421,7 @@ BYTEA           bytea           tableau d'octets (accepte les octets nuls)
     exister dans pg_hba.conf, et le sslmode du client ne doit pas
     être désactivée. Notez qu'il est aussi possible d'utiliser un
     transport crypté d'une troisième partie, tel que stunnel ou ssh, plutôt que
-    les connexions SSL natives de PostgreSQL.
+    les connexions SSL natives de PostgreSQL.
     Les mots de passe des utilisateurs sont automatiquement cryptés depuis
     la version 7.3. Pour les versions précédentes, vous devez activer l'option
     PASSWORD_ENCRYPTION dans postgresql.conf.
diff --git a/doc/src/FAQ/FAQ_german.html b/doc/src/FAQ/FAQ_german.html
index 4d842ad6fdd..924568b8fcf 100644
--- a/doc/src/FAQ/FAQ_german.html
+++ b/doc/src/FAQ/FAQ_german.html
@@ -212,7 +212,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
     Eine Portierung fÃ¼r Novell Netware 6 gibt es unter http://forge.novell.com.
 
     FÃ¼r OS/2 (eComStation) gibt es eine Version hier:
-    http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F
+    http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F
 
     1.5) Woher bekomme ich PostgreSQL?
 
@@ -223,7 +223,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
     1.6) Wo bekomme ich Support fÃ¼r PostgreSQL?
 
     Die zentrale (englischsprachige) Mailing-Liste ist:
-    mailto:pgsql-general@postgresql.org .
+    mailto:pgsql-general@postgresql.org .
 
     Die Liste ist Themen vorbehalten, die PostgreSQL betreffen. Die Anmeldung
     erfolgt mit einer Email an die Adresse pgsql-general-request@postgresql.org mit folgenden Zeilen im Text
@@ -260,7 +260,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
 
     Weitere Mailinglisten und Informationen zu PostgreSQL befinden sich auf der PostgreSQL-Homepage:
 
-http://www.postgresql.org
+http://www.postgresql.org
 
     Es gibt auÃŸerdem einen IRC-Channel bei EFNet und bei Freenode, Channel
     #PostgreSQL. Unter UNIX/Linux kÃ¶nnen Sie mit z.B.
@@ -341,7 +341,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
     1.13) Wie sende ich einen Fehlerbericht?
 
     Bitte besuchen Sie die PostgreSQL-BugTool-Seite http://www.postgresql.org/bugform.html,
-    die Hinweise und Anleitungen zur Einreichung von Fehlerberichten enthÃ¤lt.
+    die Hinweise und Anleitungen zur Einreichung von Fehlerberichten enthÃ¤lt.
 
     ÃœberprÃ¼fe auch den ftp-Server ftp://ftp.postgresql.org/pub/,
     um nachzusehen, ob es eine neuere PostgreSQL-Version oder neue Patches gibt.
@@ -475,7 +475,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
     ) und Rekall (
     http://www.thekompany.com/products/rekall/, GPL/proprietÃ¤r). Es gibt 
     auÃŸerdem phpPgAdmin (
-    http://phppgadmin.sourceforge.net/ ), eine web-basierte Schnittstelle. 
+    http://phppgadmin.sourceforge.net/ ), eine web-basierte Schnittstelle. 
 
     2.4) Welche Programmiersprachen und Schnittstellen gibt es?
 
@@ -500,7 +500,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
     (Bereich Drivers/Interfaces) bezogen werden.
     
     
-    Administrative Fragen

+    
Administrative Fragen
 
     3.1) Wie installiere ich PostgreSQL woanders als in /usr/local/pgsql?
 
@@ -632,7 +632,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
 
     Wenn der postmaster hingegen lÃ¤uft, fÃ¼hren Sie psql in einem Fenster aus,
     ermitteln Sie die Prozessnummer (PID) des postgres-Prozesses, der von psql
-    verwendet wird (mit 
SELECT pg_backend_pid()
). Binden Sie einen Debugger an diese PID
+    verwendet wird (mit SELECT pg_backend_pid()). Binden Sie einen Debugger an diese PID
     und fÃ¼hren Sie Abfragen von psql aus. Wenn Sie den postgres-Serverstart analysieren 
     wollen, setzen Sie die Umgebungsvariable PGOPTIONS="-W n", und starten Sie 
     dann psql. Dies verzÃ¶gert den Start um n Sekunden, damit Sie einen Debugger an
@@ -728,7 +728,7 @@ href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us).
     4.2) Wie wÃ¤hle ich per SELECT-Anweisung nur die ersten paar
     Zeilen bzw. eine beliebige Zeile in einer Abfrage aus?
 
-    Vgl. die FETCH Man-Page, oder benutzen Sie SELECT ... LIMIT... .
+    
Vgl. die FETCH Man-Page, oder benutzen Sie SELECT ... LIMIT... .
 
     Selbst wenn Sie nur die ersten paar Zeilen einer Tabelle abfragen mÃ¶chten,
     muÃŸ unter UmstÃ¤nden die komplette Abfrage abgearbeitet werden. Ziehen Sie also
@@ -1123,7 +1123,7 @@ BYTEA         bytea           Bytearray mit variabler LÃ¤nge (auch fÃ¼r
     durch Block und Offset Werte zu identifizieren. TIDs
     verÃ¤ndern sich, sobald Zeilen verÃ¤ndert oder zurÃ¼ckgeladen werden. Sie
     werden in IndexeintrÃ¤gen benutzt um auf die physikalischen Zeilen zu
-    zeigen.
+    zeigen.
 
     4.16) Welche Bedeutung haben die verschiedenen AusdrÃ¼cke, die in
     PostgreSQL benutzt werden (z.B. attribute, class,...)?
diff --git a/doc/src/FAQ/FAQ_japanese.html b/doc/src/FAQ/FAQ_japanese.html
index d09dd6f1d3d..05812e8db53 100644
--- a/doc/src/FAQ/FAQ_japanese.html
+++ b/doc/src/FAQ/FAQ_japanese.html
@@ -2,9 +2,9 @@
 
 
 PostgreSQL FAQ in Japanese
+
 
 
-
 
 PostgreSQL(¥Ý¥¹¥È¥°¥ì¥¹¡¦¥¥å¡¼¡¦¥¨¥ë)¤Ë¤Ä¤¤¤Æ¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤Î²òÅú(FAQ)
 
@@ -13,20 +13,19 @@ PostgreSQL(
 ¸½ºß¤Î°Ý»ý´ÉÍý¼Ô:	Bruce Momjian (pgman@candle.pha.pa.us)

 Maintainer of Japanese Translation:	Jun Kuwamura (juk at PostgreSQL.jp)

+HREF="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp)

 
 ¤³¤ÎÊ¸½ñ¤ÎºÇ¿·ÈÇ¤Ï
-    "http://www.postgresql.org/files/documentation/faqs/FAQ.html">
+    
     http://www.postgresql.org/files/documentation/faqs/FAQ.html
 ¤Ç¸«¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
 
 ¥×¥é¥Ã¥È¥Û¡¼¥à¤ËÆÃÍ¤Î¼ÁÌä¤Ë¤Ä¤¤¤Æ¤Ï:
-    "http://www.postgresql.org/docs/faq/">
+    
     http://www.postgresql.org/docs/faq/
 
¤Ë²óÅú¤¬¤¢¤ê¤Þ¤¹¡£
 
-
-
+ (°Ê²¼¡¢Ìõ¼Ô¤Ë¤è¤ëÃí¼á¤ò [ÌõÃí¡§ ¤È ] ¤È¤Ç°Ï¤ó¤Çµ¤·¤Þ¤¹¡£)
 [ÌõÃí¡§
 	ÆüËÜ¸ìÈÇÀ½ºî¤Ë¤Ä¤¤¤Æ¤Î¥á¥â¤ÏºÇ¸åÈø¤Ø°ÜÆ°¤·¤Þ¤·¤¿¡£
@@ -42,11 +41,9 @@ HREF="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp)

 
 						2005Ç¯01·î12Æü    ·¬Â¼ ½á
 ]
-
+
 
-
 

-
 
 
°ìÈÌÅª¤Ê¼ÁÌä
 
@@ -133,15 +130,14 @@ HREF="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp)

 5.2)	PostgreSQL ÍÑ¤Ë½ñ¤¤¤¿¤Á¤ç¤Ã¤ÈÁÇÅ¨¤Ê¿·¤·¤¤·¿¤ä´Ø¿ô¤òÄó¶¡¤·¤Æ¥×¥í¥¸¥§¥¯¥È¤Ë¹×¸¥¤·¤¿¤¤¤Î¤Ç¤¹¤¬¡©

 5.3)	¥¿¥×¥ë¤òÊÖ¤¹ C¸À¸ì¤Î´Ø¿ô¤Ï¤É¤Î¤è¤¦¤Ë½ñ¤¤Þ¤¹¤«¡©

 5.4)	¥½¡¼¥¹¡¦¥Õ¥¡¥¤¥ë¤òÊÑ¹¹¤·¤Þ¤·¤¿¡£ºÆ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤âÊÑ²½¤¬¸«¤é¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©

-

 

 °ìÈÌÅª¤Ê¼ÁÌä
-
 
 
1.1)	PostgreSQL ¤È¤Ï²¿¤Ç¤¹¤«¡©  ²¿¤ÈÆÉ¤ß¤Þ¤¹¤«¡©
 
 PostgreSQL¤ÏPost-Gres-Q-L(¥Ý¥¹¥È - ¥°¥ì¥¹ - ¥¥å¡¼ - ¥¨¥ë) ¤ÈÈ¯²»¤·¤Þ¤¹¡£
 PostgreSQL ¤Ï¼¡À¤Âå DBMS ¸¦µæÍÑ¤Î¥×¥í¥È¥¿¥¤¥×¤Ç¤¢¤Ã¤¿ POSTGRES ¥Ç¡¼¥¿¥Ù¡¼¥¹´ÉÍý¥·¥¹¥Æ¥à¤Î²þÎÉÈÇ¤Ç¤¹¡Ê¤³¤Î¤¿¤á¡¢º£¤Ç¤â¤È¤¤É¤ "Postgres" ¤È¸Æ¤Ð¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡Ë¡£PostgreSQL ¤Ï POSTGRES ¤Î¶¯ÎÏ¤Ê¥Ç¡¼¥¿¡¦¥â¥Ç¥ë¤ÈËÉÙ¤Ê¥Ç¡¼¥¿¡¦¥¿¥¤¥×(·¿)¤òÊÝ»ý¤·¤Ê¤¬¤é¡¢POSTGRES ¤Ç»È¤ï¤ì¤¿ PostQuel Ìä¤¤¹ç¤ï¤»¸À¸ì¤ò¡¢³ÈÄ¥¤·¤¿ SQL ¤Î¥µ¥Ö¥»¥Ã¥È¤ËÃÖ¤´¹¤¨¤Æ¤¤¤Þ¤¹¡£PostgreSQL ¤ÏÌµÎÁ¤Ç´°Á´¤Ê¥½¡¼¥¹¤òÍøÍÑ¤Ç¤¤Þ¤¹¡£
+
 
 PostgreSQL ¤Î³«È¯¤Ï¡¢PostgreSQL ³«È¯¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ë»²²Ã¤·¤Æ¤¤¤ë³«È¯¼ÔÃ£¤Î¥Á¡¼¥à¤Ç¤¹¤Ù¤Æ¹Ô¤Ê¤ï¤ì¤Æ¤¤¤Þ¤¹¡£¸½ºß¤ÎºÂÄ¹¤Ï Marc G. Fournier (scrappy@PostgreSQL.org )¤Ç¤¹¡£(²¼µ¤Î1.6Àá¤Ë»²²Ã¤Î»ÅÊý¤¬¤¢¤ê¤Þ¤¹¡£)¸½ºß¡¢¤³¤Î¥Á¡¼¥à¤¬ PostgreSQL ³«È¯¤Î¤¹¤Ù¤Æ¤ÎÌÌÅÝ¤ò¤ß¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥Á¡¼¥à¤Ï¥³¥ß¥å¥Ë¥Æ¥£¥×¥í¥¸¥§¥¯¥È¤Ç¤¢¤ê¡¢¤¤¤«¤Ê¤ë´ë¶È¤Ë¤è¤Ã¤Æ¤âÀ©¸æ¤ò¼õ¤±¤Þ¤»¤ó¡£»²²Ã¤·¤¿¤±¤ì¤Ð¡¢
@@ -150,18 +146,20 @@ HREF="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp)

 
 
 Postgres95-1.01 ¤ÎÃæ¿´Åª¤Ê³«È¯¼Ô¤Ï Andrew Yu ¤È Jolly Chen ¤Ç¤·¤¿¤¬¡¢¤½¤ÎÂ¾ÂçÀª¤Î¿Í¡¹¤¬¤³¤Î¥³¡¼¥É¤Î°Ü¿¢¡¢¥Æ¥¹¥È¡¢¥Ç¥Ð¥°¡¢¤ª¤è¤Ó¡¢²þÎÉ¤Ë»²²Ã¤·¤Þ¤·¤¿¡£PostgreSQL ¤ÎÇÉÀ¸¸µ¥³¡¼¥É¤Ç¤¢¤ë Postgres ¤Ï¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø¥Ð¡¼¥¯¥ì¥¤¹»¤Ë¤ª¤¤¤Æ¡¢ Michael Stonebraker ¶µ¼ø¤Î»Ø´ø¤Î¤â¤È¡¢Â¿¤¯¤Î³ØÀ¸¡¢Â´¶ÈÀ¸¡¢ËÜ¿¦¤Î¥×¥í¥°¥é¥Þ¤¿¤Á¤ÎÅØÎÏ¤Ë¤è¤êºî¤é¤ì¤Þ¤·¤¿¡£
+
 
 ¥Ð¡¼¥¯¥ì¥¤¤Ë¤ª¤±¤ë¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Î¤â¤È¤ÎÌ¾Á°¤Ï Postgres ¤Ç¤·¤¿¤¬¡¢SQL ¤Îµ¡Ç½¤¬ÄÉ²Ã¤µ¤ì¤¿ 1995 Ç¯¤Ë¤½¤ÎÌ¾Á°¤Ï Postgres95 ¤ËÊÑ¹¹¤µ¤ì¡¢1996 Ç¯¤Î½ª¤ê¤Ë¤½¤ÎÌ¾Á°¤Ï PostgreSQL ¤ËÊÑ¹¹¤µ¤ì¤Þ¤·¤¿¡£
+
 
-
 
1.2)	PostgreSQL ¤ÎÃøºî¸¢¤Ï¤É¤¦¤Ê¤Ã¤Æ¤Þ¤¹¤«¡©
 
  PostgreSQL ¤Ï²¼µ¤ÎÃøºî¸¢¤Ë½¾¤¤¤Þ¤¹¡£
-
+
+     [ÌõÃí¡§
         ÀµÊ¸¤Ï±Ñ¸ì¤Ç¤¹¡£»²¹Í¤È¤·¤Æ¡¢ÌõÊ¸¤òÊ»µ·ÇºÜ¤·¤Þ¤¹¡£
     ]
-
+
 
 PostgreSQL Data Base Management System
 
@@ -187,7 +185,7 @@ IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO
 OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
 MODIFICATIONS.
 
-+ 	POSTGRESQL ¥Ç¡¼¥¿¥Ù¡¼¥¹´ÉÍý¥·¥¹¥Æ¥à
 
 	ÉôÊ¬ÅªÃøºî¸¢ (c) 1996-2004, PostgreSQL¹ñºÝ³«È¯¥Á¡¼¥à
@@ -214,7 +212,7 @@ MODIFICATIONS.
 	Ãøºî¸¢¤Ë´Ø¤¹¤ëÀµÊ¸¤Ï¾åµ¤Î±Ñ¸ì¤Ë¤è¤ëÉ½µ¤Ç¤¹¡£ÆüËÜ¸ìÌõ¤Ï¤¢¤¯¤Þ¤Ç
 	»²¹Í¤Ç¤¹¡£
     ]
-
+
 
 ¾åµ¤ÏBSD¥é¥¤¥»¥ó¥¹¤Ç¸Å¤¥ª¡¼¥×¥ó¥½¡¼¥¹¤Î¥é¥¤¥»¥ó¥¹¤Ç¤¹¡£¥½¡¼¥¹¥³¡¼¥É
 ¤¬¤É¤Î¤è¤¦¤Ë»È¤ï¤ì¤è¤¦¤È¤âÀ©¸Â¤·¤Þ¤»¤ó¡£¹¥¤Þ¤·¤¤¤³¤È¤Ê¤Î¤Ç¡¢²æ¡¹¤â¤½¤ì¤ò
@@ -225,7 +223,6 @@ MODIFICATIONS.
 
 °ìÈÌÅª¤Ë¡¢ºÇ¶á¤ÎUnix¸ß´¹¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤¢¤ì¤ÐPostgreSQL¤ò²ÔÆ¯¤µ¤»¤é¤ì¤ë¤Ï¤º¤Ç¤¹¡£¥ê¥ê¡¼¥¹¤Î»þÅÀ¤Ç¼ÂºÝ¤Ë¥Æ¥¹¥È¤ò¹Ô¤Ê¤Ã¤¿¤³¤È¤ÎÊó¹ð¤¬¤Ê¤µ¤ì¤¿¥×¥é¥Ã¥È¥Û¡¼¥à¤Ë¤Ä¤¤¤Æ¤Ï¥¤¥ó¥¹¥È¡¼¥ë¼ê°ú½ñ¤ËÎóµó¤·¤Æ¤¢¤ê¤Þ¤¹¡£
 
-
 
1.4)	Unix°Ê³°¤Î°Ü¿¢ÈÇ¤Ç»È¤¨¤ë¤â¤Î¤Ï¡©
 
 ¥Ð¡¼¥¸¥ç¥ó8.0¤Ë¤Ê¤ê¡¢PostgreSQL ¤Ï¡¢Win2000, WinXP, Win2003¤Ê¤É¤Î Microsoft Windows NT¥Ù¡¼¥¹¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¥Í¥¤¥Æ¥£¥Ö¤ËÁö¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
@@ -233,18 +230,18 @@ MODIFICATIONS.
 Windows (Win95, Win98, WinMe)¤Ê¤É¡¢MSDOS¥Ù¡¼¥¹¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢Cygwin ¤ò»È¤Ã¤ÆPostgreSQL¤òÁö¤é¤»¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
 
 
-+     [ÌõÃí
 	pgInstaller ¤ÎÆþ¼ê¤ÏFTP¥ß¥é¡¼¥µ¥¤¥È¤Î win32 ¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤â²ÄÇ½¤Ç¤¹¡£
 	    http://www.postgresql.org/mirrors-ftp.html
     ]
-
+
 
     ¼¡¤Î¥µ¥¤¥È¤Ë Novell Netware 6 ¤Ø¤Î°Ü¿¢¤â¤¢¤ê¤Þ¤¹¡£
     http://forge.novell.com
     ¤Þ¤¿¡¢OS/2 (eComStation) ¥Ð¡¼¥¸¥ç¥ó¤Ï¡¢
-    http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F¤Ë¤¢¤ê¤Þ¤¹¡£
+    "http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F">
+    http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F¤Ë¤¢¤ê¤Þ¤¹¡£
 

 
 
@@ -256,7 +253,7 @@ href="ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/
 ¤Ç¤¹¡£
 ¥ß¥é¡¼¥µ¥¤¥È¤Ë¤Ä¤¤¤Æ¤Ï¡¢²æ¡¹¤Î¥á¥¤¥ó Web ¥Ú¡¼¥¸¤ò¤´Í÷²¼¤µ¤¤¡£
 
-+     [ÌõÃí:
 
 	°Ê²¼¤ÏÆüËÜ¤Î¥ß¥é¡¼¥µ¥¤¥È¤Ç¤¹:
@@ -274,7 +271,7 @@ href="ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/
        Japan: ftp://ring.so-net.ne.jp/pub/misc/db/PostgreSQL/
        Japan: ftp://ring.aist.go.jp/pub/misc/db/PostgreSQL/
     ]
-
+
 
 1.6)	¥µ¥Ý¡¼¥È¤Ï¤É¤³¤Ç¼õ¤±¤é¤ì¤Þ¤¹¤«¡©
 
@@ -292,33 +289,35 @@ href="ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/
 	end
 
 
-¤È½ñ¤¤¤Æ  pgsql-general-digest-request@PostgreSQL.org ¤ØÅÅ»Ò¥á¡¼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
+¤È½ñ¤¤¤Æ  pgsql-general-digest-request@PostgreSQL.org ¤ØÅÅ»Ò¥á¡¼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
 
  ¥À¥¤¥¸¥§¥¹¥ÈÈÇ¤Ï¡¢¥á¥¤¥ó¥ê¥¹¥È¤Ç¼õ¿®¤¹¤ë¥á¥Ã¥»¡¼¥¸¤¬ 30k ÄøÅÙÎ¯¤ëËè¤Ë¥À¥¤¥¸¥§¥¹¥ÈÈÇ¥ê¥¹¥È¤Î¥á¥ó¥Ð¡¼¤ËÁ÷ÉÕ¤µ¤ì¤Þ¤¹¡£
 
  ¥Ð¥°¥ì¥Ý¡¼¥ÈÍÑ¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤â¤¢¤ê¤Þ¤¹¡£¤³¤Î¥ê¥¹¥È¤Ø¤Î»²²Ã¤Ï "ËÜÊ¸" ¤Ë¡§
+
  	subscribe
 	end
 
+
 ¤È½ñ¤¤¤Æpgsql-bugs-request@PostgreSQL.org
 
 ¤ØÅÅ»Ò¥á¡¼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
 
  ³«È¯¼Ô¤ÎµÄÏÀ¤Î¤¿¤á¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤âÍøÍÑ¤Ç¤¤Þ¤¹¡£¤³¤Î¥ê¥¹¥È¤Ø¤Î»²²Ã¤ÏÅÅ»Ò¥á¡¼¥ë¤ÎËÜÊ¸¤Ë¡§
+
  	subscribe
 	end
 
 
-¤È½ñ¤¤¤Æ¡¢pgsql-hackers-request@PostgreSQL.org¤ØÅÅ»Ò¥á¡¼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
+¤È½ñ¤¤¤Æ¡¢pgsql-hackers-request@PostgreSQL.org¤ØÅÅ»Ò¥á¡¼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
 
-PostgreSQL ¤Ë¤Ä¤¤¤Æ¤â¤Ã¤È¾Ü¤·¤¯ÃÎ¤ê¤¿¤±¤ì¤Ð¡¢¼¡¤Î PostgreSQL WWW¥Û¡¼¥à¥Ú¡¼¥¸¤«¤é¤¿¤É¤ì¤Þ¤¹¡§
 
-		http://www.PostgreSQL.org
+		http://www.PostgreSQL.org
 
-
 ¥á¥¸¥ã¡¼¤ÊIRC ¥Á¥ã¥ó¥Í¥ë¤Ï¡¢Freenode (irc.freenode.net)¤Î
 #PostgreSQL ¤È¤¤¤¦¥Á¥ã¥ó¥Í¥ë¤Ç¤¹¡£
 UNIX ¥³¥Þ¥ó¥É¤Ç¡¢
@@ -329,8 +328,7 @@ UNIX 
 EFNet¤Ë¤âPostgreSQL¥Á¥ã¥ó¥Í¥ë¤¬¤¢¤ê¤Þ¤¹¡£
 
 
-
-
+     [ÌõÃí:
 	  1999Ç¯7·î23Æü¡¢ÆüËÜ¥Ý¥¹¥È¥°¥ì¥¹¥æ¡¼¥¶¡¼²ñ¡¢Î¬¾ÎJPUG¤¬ÀßÎ©¤µ¤ì¤Þ¤·¤¿¡£
 	JPUG ¤ÏÈó±ÄÍøÁÈ¿¥¤Ç¡¢PostgreSQL¤òÍøÍÑ¤¹¤ë¿ÍÃ£¤ÎÁê¸ß¶¨ÎÏ¤Î¾ì¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£  
@@ -341,7 +339,7 @@ EFNet
 	¤ò¤´Í÷¤¯¤À¤µ¤¤¡£²ñ°÷ÅÐÏ¿¤â²ÄÇ½¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
 
 	ÆüËÜ¸ì¤ÎIRC¥Á¥ã¥ó¥Í¥ë '#PostgreSQL*jp' ¤âÂ¸ºß¤·¤Þ¤¹¡£
-
+
 
 
 ¾¦ÍÑ¥µ¥Ý¡¼¥È²ñ¼Ò¤Î¥ê¥¹¥È¤Ïhttp://techdocs.postgresql.org/companies.php¤Ë¤¢¤ê¤Þ¤¹¡£
@@ -358,24 +356,25 @@ PostgreSQL 
 
  ÇÛÉÕ¤ÎÃæ¤Ë¡¢¤¤¤¯¤Ä¤«¤Î¥Þ¥Ë¥å¥¢¥ë¤È¥ª¥ó¥é¥¤¥ó¡¦¥Þ¥Ë¥å¥¢¥ë(¥Þ¥Ë¥å¥¢¥ë¡¦¥Ú¡¼¥¸)¤ª¤è¤Ó¤¤¤¯¤Ä¤«¤Î¾®¤µ¤Ê¥Æ¥¹¥ÈÎãÂê¤¬´Þ¤Þ¤ì¤Þ¤¹¡£/doc ¥Ç¥£¥ì¥¯¥È¥ê¤ò¤´Í÷²¼¤µ¤¤¡£¤Þ¤¿¡¢¥Þ¥Ë¥å¥¢¥ë¤Ï¡¢http://www.ca.PostgreSQL.org/docs/¤Ç¥ª¥ó¥é¥¤¥ó¤Ç¤â±ÜÍ÷¤Ç¤¤Þ¤¹¡£
 
-+     [ÌõÃí:
 	¡Ê³ô¡ËSRA¤ÈÆüËÜPostgreSQL¥æ¡¼¥¶²ñ¤ÇËÝÌõ¤µ¤ì¡¢
 	¡ÖPostgreSQL ¥ª¥Õ¥£¥·¥ã¥ë¥Þ¥Ë¥å¥¢¥ë¡×
 	¤È¤·¤Æ½ÐÈÇ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
     ]
-
+
 
 
 ¥ª¥ó¥é¥¤¥ó¤Ç»²¾È¤Ç¤¤ë PostgreSQL ¤ÎËÜ¤â2ºý¤¢¤ê¤Þ¤¹¡£http://www.PostgreSQL.org/docs/awbook.html
-
+
+     [ÌõÃí:
 	ÆüËÜ¥Ý¥¹¥È¥°¥ì¥¹¥æ¡¼¥¶¡¼²ñ¤Î	¡ÖPostgreSQL BookËÝÌõÊ¬²Ê²ñ¡×
 	¤Ë¤ÆËÝÌõ¤µ¤ì¤Þ¤·¤¿¡£
     ]
-
-
+
+
     ¤ª¤è¤Ó¡¢ http://www.commandprompt.com/ppbook/
 ¤Ç¤¹¡£
@@ -415,14 +414,13 @@ PostgreSQL
 
 http://www.PostgreSQL.org/docs/awbook.html
 ¤Ë¤¢¤ëPostgreSQLËÜ¤Ç SQL ¤ò¶µ¤¨¤Æ¤¤¤Þ¤¹¡£
-
-
+
+     [ÌõÃí:
 	ÆüËÜ¥Ý¥¹¥È¥°¥ì¥¹¥æ¡¼¥¶¡¼²ñ¤Î	¡ÖPostgreSQL BookËÝÌõÊ¬²Ê²ñ¡×
 	¤Ë¤ÆËÝÌõ¤µ¤ì½ÐÈÇ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
     ]
-
-
+
 
 
 ¤½¤ÎÂ¾¤Ë¤â PostgreSQLËÜ¤È¤·¤Æ¡¢
 ¤Î¤è¤¦¤Ê¤Î¤â¤¢¤ê¤Þ¤¹¡£
 

 
-
-+     [ÌõÃí:
 	 ÀÐ°æÃ£É×»á¤Ë¤è¤ëÆüËÜ¸ì¤Î»²¹ÍÊ¸¸¥¤Î¾Ò²ð¥Ú¡¼¥¸
 		http://www.SRA.co.jp/people/t-ishii/PostgreSQL/doc-jp/index.html
@@ -465,8 +462,7 @@ http://www.PostgreSQL.org/docs/awbook.html
 		http://www.wakhok.ac.jp/DB/DB.html
 	¤â¥ª¥ó¥é¥¤¥ó¤ÇÆÉ¤à¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
     ]
-
-
+
 
 1.11)	PostgreSQL¤ÏÀ¾Îñ2000Ç¯ÌäÂê(Y2K)¤ËÂÐ±þ¤·¤Æ¤¤¤Þ¤¹¤«¡©
 
@@ -536,6 +532,7 @@ http://www.PostgreSQL.org/docs/awbook.html
 ¼Á¤ÎÎÉ¤¤´ðÈ×¤Ï¡¢¥ª¡¼¥×¥ó¥½¡¼¥¹¡¦¥×¥í¥¸¥§¥¯¥È¤Ë¤È¤Ã¤Æ¤Ï¤È¤Æ¤âÂçÀÚ¤Ê¤â¤Î¤Ç¡¢¥×¥í¥¸¥§¥¯¥È¤¬Á°¿Ê¤¹¤ëÀª¤¤¤ò¼º¤Ã¤ÆÊ¬Îö¤¹¤ë¤Î¤ò²óÈò¤·¤Þ¤¹¡£
 
 ¤â¤Á¤í¤ó¡¢¤³¤Î´ðÈ×¤Ï°Â¤¤¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£°Ý»ý¤·Â³¤±¤ë¤¿¤á¤Ë¤ÏËè·î¤¢¤ë¤¤¤Ï°ì»þÅª¤Ë·ÐÈñ¤¬¤«¤«¤ê¤Þ¤¹¡£¤â¤·¡¢¤¢¤Ê¤¿¤ä¤¢¤Ê¤¿¤Î²ñ¼Ò¤Ë¡¢¤³¤¦¤·¤¿ÅØÎÏ¤Î¤¿¤á¤Î»ñ¶â¤Î±ç½õ¤ò»Ü¤¹¤³¤È¤¬¤Ç¤¤ë¤è¤¦¤Ç¤·¤¿¤é¡¢http://store.pgsql.com/shopping/¤«¤é´óÉÕ¤ò¤ª´ê¤¤¤·¤Þ¤¹¡£
+
 
 ¤Þ¤¿¡¢Web¥Ú¡¼¥¸¤Ë¤Ï PostgreSQL,Inc ¤È¤¢¤ê¤Þ¤¹¤¬¡¢¤½¤³¤Î "¹×¸¥(contributions)"¤È¤¤¤¦¹àÌÜ¤Ï¡¢ PostgreSQL ¥×¥í¥¸¥§¥¯¥È¤ò»Ù±ç¤¹¤ë¤À¤±¤Î¤¿¤á¤Ç¡¢·è¤·¤ÆÆÃÄê¤Î²ñ¼Ò¤Î¤¿¤á¤Î»ñ¶â¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤â¤·¡¢¾®ÀÚ¼ê(check)¤ÎÊý¤¬ÅÔ¹ç¤è¤±¤ì¤ÐÏ¢ÍíÀè¤Î½»½ê¤Ø¤ªÁ÷¤ê²¼¤µ¤¤¡£
 
@@ -546,10 +543,8 @@ http://www.PostgreSQL.org/docs/awbook.html
 ¤Ø¤ªÁ÷¤ê¤¯¤À¤µ¤¤¡£
 
 
-
 

 ¥æ¡¼¥¶¡¼¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä
-
 
 
2.1)	PostgreSQL ¤Î¤¿¤á¤Î ODBC ¥É¥é¥¤¥Ð¡¼¤Ï¤¢¤ê¤Þ¤¹¤«¡©
 
@@ -563,26 +558,27 @@ http://www.PostgreSQL.org/docs/awbook.html
 
 
  OpenLink ODBC ¤Ï http://www.openlinksw.com/¤«¤éÆþ¼ê¤Ç¤¤Þ¤¹¡£É¸½àÅª¤Ê ODBC ¥¯¥é¥¤¥¢¥ó¥È¡¦¥½¥Õ¥È¥¦¥§¥¢¤Ç»È¤¨¤Þ¤¹¤Î¤Ç¡¢»Ù±ç¤·¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥×¥é¥Ã¥È¥Û¡¼¥à(Win, Mac, Unix, VMS)¤«¤é PostgreSQL ¤Î ODBC ¤¬ÍøÍÑ¤Ç¤¤Þ¤¹¡£
+
 
  ¤¿¤Ö¤óÈà¤é¤Ï¡¢¾¦ÍÑÉÊ¼Á¤Î¥µ¥Ý¡¼¥È¤ÎÉ¬Í×¤Ê¿Í¡¹¤ËÇä¤Ã¤Æ¤¤¤ë¤È»×¤¤¤Þ¤¹¤¬¡¢
     ¥Õ¥ê¡¼¥¦¥§¥¢ÈÇ¤Ï¤¤¤Ä¤Ç¤âÆþ¼ê²ÄÇ½¤Î¤è¤¦¤Ç¤¹¡£¼ÁÌä¤Ï¡¢postgres95@openlink.co.uk
     ¤ØÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
-
+
 
 Programmer's Guide
 ¤Î ODBC ¤Î¾Ï¤â¤´Í÷¤¯¤À¤µ¤¤¡£
+
 
-
-
 
2.2)	PostgreSQL ¤ò Web ¥Ú¡¼¥¸¤ÈÏ¢·È¤µ¤»¤ë¤Ë¤Ï¤É¤ó¤Ê¥Ä¡¼¥ë¤¬¤¢¤ê¤Þ¤¹¤«¡©
 
 
  ¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÎ¢¤Ë»ý¤Ä Web ¥Ú¡¼¥¸¤Ë¤Ä¤¤¤Æ¤ÎÁÇÀ²¤é¤·¤¤¾Ò²ð¤¬¡¢

     http://www.webreview.com¤Ë¤¢¤ê¤Þ¤¹¡£
  Web ¤Ø¤Î³ÈÄ¥¤Î¤¿¤á¤Ë¤Ï¡¢PHP ¤¬Âî±Û¤·¤¿¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£http://www.php.net/¤Ë¤¢¤ê¤Þ¤¹¡£
+
 
-+     [ÌõÃí:
 	  PHP¤Ë´Ø¤¹¤ëÆüËÜ¸ì¤Î¾ðÊó¤Ï¡¢2000Ç¯4·î19Æü¤ËÈ¯Â¤·¤¿ÆüËÜPHP¥æ¡¼¥¶²ñ¤Î¥µ¥¤¥È
 		http://www.php.gr.jp/
@@ -590,11 +586,12 @@ Programmer's Guide
 		http://www.geocities.jp/rui_hirokawa/php/
 	¤Ë¤«¤Ê¤ê¤Þ¤È¤á¤é¤ì¤Æ¤¤¤Þ¤¹¡£
     ]
-
+
 
  ½èÍý¤¬Ê£»¨¤Ê¾ì¹ç¡¢Â¿¤¯¤Î¿Í¤Ï Perl ¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤È CGI.pm ¤« mod_perl ¤ò»È¤¤¤Þ¤¹¡£
+
 
-+     [ÌõÃí:
 	WDB ¤Ï¡¢Web ¤«¤é DataBase ¤Ø¤Î Perl ¤Î Interface ¤Ç¤¹¡£
 	wdb-p95 ¤Ø¤Î¥ê¥ó¥¯¤ÏÀÚ¤ì¤Æ¤·¤Þ¤Ã¤Æ¤¤¤Þ¤¹¡£¤ª¤½¤é¤¯¡¢Perl DBI ·ÐÍ³¤Ç DBD::Pg ¤ÎÍøÍÑ¤¬²ÄÇ½¤È»×¤ï¤ì¤Þ¤¹¡£
@@ -604,9 +601,8 @@ Programmer's Guide
 		http://www.i-con.dk/wdb/
 	¤È¤¬¤¢¤ê¤Þ¤¹¡£¤½¤Î·Ð°Þ¤Ï¤è¤¯¤ï¤«¤ê¤Þ¤»¤ó¡£
     ]
-
+
 
-
 
2.3)	PostgreSQL ¤Ë¥°¥é¥Õ¥£¥«¥ë¡¦¥æ¡¼¥¶¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Ï¤¢¤ê¤Þ¤¹¤«¡©
 
   ¤â¤Á¤í¤ó¡¢PostgreSQL ¤Ø¤Î¥°¥é¥Õ¥£¥«¥ë¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤¬¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£
@@ -626,12 +622,12 @@ RHDB Admin (
     http://phppgadmin.sourceforge.net/ ) ¤ÏPostgreSQL¤Ø¤ÎWeb¥Ù¡¼¥¹¤Î
 ¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤òÄó¶¡¤·¤Þ¤¹¡£
+
 
 ¤è¤ê¾ÜºÙ¤Ê¥ê¥¹¥È¤Ë¤Ä¤¤¤Æ¤Ï¡¢http://techdocs.postgresql.org/guides/GUITools
     ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
 
-
 
2.4)	¤É¤Î¤è¤¦¤Ê¸À¸ì¤Ç PostgreSQL ¤ÈÄÌ¿®¤Ç¤¤¹¤«¡©
 
 
@@ -640,42 +636,41 @@ PhpPgAdmin (
 
 
 °Ê²¼¤Î¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤ÏPostgreSQL¤ÎÇÛÉÛ¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
+
 
 
-C (libpq)
-
Ëä¤á¹þ¤ßC (ecpg)
-
Java (jdbc)
-Python (PyGreSQL)
-
TCL (libpgtcl)
+
C (libpq)
+Ëä¤á¹þ¤ßC (ecpg)
+Java (jdbc)
+Python (PyGreSQL)
+TCL (libpgtcl)
 
-    ¤½¤ÎÂ¾¤ÎÍøÍÑ²ÄÇ½¤Ê¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Ï ¤½¤ÎÂ¾¤ÎÍøÍÑ²ÄÇ½¤Ê¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Ï  
 http://gborg.postgresql.org
 ¤ÎDrivers/Interfaces¤Î¥»¥¯¥·¥ç¥ó¤Ë¤¢¤ê¤Þ¤¹¡£
     
 
-+     [ÌõÃí¡§
 	±Ê°Â¸ç»Ë¤µ¤ó¤Ï Palm ÈÇ¤Î libpq ¤ò³«È¯¤µ¤ì¤Þ¤·¤¿¡£
 		http://www.snaga.org/libpq/
     ]
-
+
 
-
 

 ´ÉÍý¾å¤Î¼ÁÌä
-
 
 
3.1)	¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð /usr/local/pgsql °Ê³°¤Î¾ì½ê¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤¤Þ¤¹¤«¡©
 
  ´ÊÃ±¤ÊÊýË¡¤Ï¡¢ configure ¤òÁö¤é¤»¤ë¤È¤¤Ë --prefix ¥ª¥×¥·¥ç¥ó¤ò»ØÄê¤¹¤ë¤³¤È¤Ç¤¹¡£
+
 
-
 
3.2)	postmaster ¤òÁö¤é¤»¤ë¤È¡¢Bad System Call ¤È¤«¥³¥¢¡¦¥À¥ó¥×¤·¤¿¤È¤Î¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©
 
 
  ¤µ¤Þ¤¶¤Þ¤ÊÌäÂê¤¬¹Í¤¨¤é¤ì¤Þ¤¹¤¬¡¢¤Þ¤ººÇ½é¤Ë¤¢¤Ê¤¿¤Î¥«¡¼¥Í¥ë¤Ë System V IPC ¤Î³ÈÄ¥¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤«¤ò³ÎÇ§¤·¤Æ¸«¤Æ¤¯¤À¤µ¤¤¡£PostgreSQL ¤Ï¥«¡¼¥Í¥ë¤Ë¤è¤ë¶¦Í¥á¥â¥ê¡¼¤È¥»¥Þ¥Õ¥©¤Î¥µ¥Ý¡¼¥È¤òÉ¬Í×¤È¤·¤Þ¤¹¡£
 
-

+
 3.3)	postmaster ¤òÁö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢IpcMemoryCreate ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©
 
 
@@ -686,11 +681,11 @@ PhpPgAdmin (
 ¤Ë¶¦Í¥á¥â¥ê¡¼¤È¥»¥Þ¥Õ¥©¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤Î¾ÜºÙ¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¤´Í÷¤¯¤À¤µ¤¤¡£
 
 
-
 3.4)	postmaster¤òÁö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢IpcSemaphoreCreate ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©
 
 
 ¤â¤·¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬IpcSemaphoreCreate: semget failed (No space left on device)¤Ç¤¢¤ì¤Ð¡¢¥«¡¼¥Í¥ë¤¬½½Ê¬¤Ê¥»¥Þ¥Õ¥©¤ò»È¤¨¤ë¤è¤¦¤Ë¹½À®¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£Postgres¤ÏÀøºßÅª¤Ê¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹Ëè¤Ë°ì¤Ä¤Î¥»¥Þ¥Õ¥©¤òÉ¬Í×¤È¤·¤Þ¤¹¡£¤È¤ê¤¢¤¨¤º¤Î²ò·èºö¤Ïpostmaster¤òµ¯Æ°¤¹¤ë¤È¤¤Ë¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹¤Î¿ô¤ò¤è¤ê¾¯¤Ê¤¯À©¸Â¤ò¤¹¤ë¤³¤È¤Ç¤¹¡£´ûÄêÃÍ¤Î32¤è¤ê¾®¤µ¤Ê¿ô¤Î¥Ñ¥é¥á¡¼¥¿¤ò-N¤Ç»È¤¤¤Þ¤¹¡£¤è¤ê¹±µ×Åª¤Ê²ò·èºö¤Ï¡¢¥«¡¼¥Í¥ë¤ÎSEMMNS ¤È SEMMNI ¥Ñ¥é¥á¡¼¥¿¤òÁý¤ä¤¹¤³¤È¤Ç¤¹¡£
+
 
     ÁàºîÉÔÇ½¤Î¥»¥Þ¥Õ¥©¤â²áÅÙ¤Ê¥Ç¡¼¥¿¥Ù¡¼¥¹¥¢¥¯¥»¥¹¤Î´Ö¤Ë¥¯¥é¥Ã¥·¥å¤ò
 µ¯¤³¤¹²ÄÇ½À¤¬¤¢¤ê¤Þ¤¹¡£
@@ -699,7 +694,6 @@ PhpPgAdmin (
 
¤â¤·¡¢¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬¤Ê¤Ë¤«Â¾¤Î¤â¤Î¤Ç¤¢¤ì¤Ð¡¢¥«¡¼¥Í¥ë¤Î¹½À®¤Ç¤Þ¤Ã¤¿¤¯¥»¥Þ¥Õ¥©¤Î¥µ¥Ý¡¼¥È¤ò¤·¤Æ¤¤¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
 PostgreSQL Administrator's Guide ¤Ë¶¦Í¥á¥â¥ê¡¼¤È¥»¥Þ¥Õ¥©¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤Î¾ÜºÙ¤¬¤¢¤ê¤Þ¤¹¡£

 
-
 
 3.5)	Â¾¤Î¥Û¥¹¥È¤«¤é¤ÎÀÜÂ³¤Ï¤É¤Î¤è¤¦¤ËÀ©¸æ¤·¤Þ¤¹¤«¡©
 
@@ -707,56 +701,68 @@ PostgreSQL Administrator's Guide 
 	´ûÄêÃÍ¤Ç¤Ï¡¢PostgreSQL ¤Ï Unix ¥É¥á¥¤¥ó¥½¥±¥Ã¥È¡¢¤Þ¤¿¤Ï¡¢TCP/IPÀÜÂ³¤Î¥í¡¼¥«¥ë¥Þ¥·¥ó¤«¤é¤ÎÀÜÂ³¤·¤«µö¤·¤Þ¤»¤ó¡£postgresql.conf ¤ÎÃæ¤Î listen_addresses ¤ò½¤Àµ¤·¡¢¤«¤Ä¡¢$PGDATA/pg_hba.conf ¥Õ¥¡¥¤¥ë¤òÅ¬ÀÚ¤ËÄ¾¤·¤Æ¡¢¥Û¥¹¥È¼çÆ³·¿Ç§¾Ú¤òÍ¸ú¤Ë¤·¤Ê¤¤¤«¤®¤ê¤Ï¡¢Â¾¤Î¥Þ¥·¥ó¤«¤é¤ÏÀÜÂ³¤Ç¤¤Ê¤¤¤Ç¤·¤ç¤¦¡£
 
 
-
 
3.6)	¤è¤êÎÉ¤¤ÀÇ½¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥¨¥ó¥¸¥ó¤ò¤É¤Î¤è¤¦¤ËÄ´À°¤¹¤ì¤ÐÎÉ¤¤¤Ç¤¹¤«¡©
 
 
  ³Î¤«¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤ÏÌä¤¤¹ç¤ï¤»¤ÎÂ®ÅÙ¤òÁý¤·¤Þ¤¹¡£EXPLAIN ANALYZE¥³¥Þ¥ó¥É¤Ç PostgreSQL ¤¬¤É¤Î¤è¤¦¤Ë¤¢¤Ê¤¿¤ÎÌä¤¤¹ç¤ï¤»¤òËÝÌõ¤·¤Æ¤¤¤ë¤«¤ò¸«¤ë¤³¤È¤¬¤Ç¤¡¢¤½¤·¤Æ¡¢¤É¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤¬»È¤ï¤ì¤Æ¤¤¤ë¤«¤ò¸«¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
+
 ¤â¤· INSERT ¤òÂ¿ÍÑ¤·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢COPY ¥³¥Þ¥ó¥É¤ò»È¤Ã¤ÆÂç¤¤Ê¥Ð¥Ã¥Á½èÍý¤Ç¤½¤ì¤ò¹Ô¤Ê¤¦¤³¤È¤ò¸¡Æ¤¤·¤Æ²¼¤µ¤¤¡£¤³¤ì¤Ï¡¢INSERT ¤òÊÌ¡¹¤Ë¹Ô¤Ê¤¦¤è¤ê¤â¤Ã¤È¹âÂ®¤Ç¤¹¡£¼¡¤Ë¡¢BEGIN WORK/COMMIT ¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¡¦¥Ö¥í¥Ã¥¯¤ÎÃæ¤ËÌµ¤¤Ê¸¤Ï¡¢¤½¤ì¤é¼«¿È¤¬¤½¤ì¤¾¤ì¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤ËÆþ¤Ã¤Æ¤¤¤ë¤È¸«¤Ê¤µ¤ì¤Þ¤¹¡£¤¤¤¯¤Ä¤«¤ÎÊ¸¤ò°ì¤Ä¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¡¦¥Ö¥í¥Ã¥¯¤ÎÃæ¤Ç¹Ô¤Ê¤¦¤³¤È¤ò¹Í¤¨¤Æ²¼¤µ¤¤¡£¤³¤ì¤Ë¤è¤ê¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤Î¥ª¡¼¥Ð¡¼¥Ø¥Ã¥É¤¬¸º¤ê¤Þ¤¹¡£¤Þ¤¿¡¢Âç¤¤Ê¥Ç¡¼¥¿¤ÎÊÑ¹¹¤ò¹Ô¤Ê¤¦ºÝ¤Ï¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò°ìÅÙ³°¤·¤Æ¡¢ºî¤êÄ¾¤¹¤³¤È¤ò¹Í¤¨¤Æ¤ß¤Æ²¼¤µ¤¤¡£
+
 
  
     Administration Guide/Server Run-time Environment/Run-time
     Configuration¤Ë¤Ï¡¢
 ¥Á¥å¡¼¥Ë¥ó¥°¤Î¥ª¥×¥·¥ç¥ó¤¬¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£fsync¥ª¥×¥·¥ç¥ó¤Çfsync() ¤òÌµ¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£¤³¤ì¤Ë¤è¤Ã¤Æ¡¢³Æ¥È¥é¥ó¥¶¥¯¥·¥ç¥óËè¤Ë fsync() ¤Ç¥Ç¥£¥¹¥¯¤ò¹¹¿·¤¹¤ë¤Î¤ò»ß¤á¤µ¤»¤Þ¤¹¡£
+
 
  shared_buffers¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¥Ð¥Ã¥¯¥¨¥ó¥É¡¦¥×¥í¥»¥¹¤Ë¤è¤ê»È¤ï¤ì¤ë¶¦Í¥á¥â¥ê¡¼¡¦¥Ð¥Ã¥Õ¥¡¤òÂç¤¤¯¤¹¤ë¤³¤È¤â¤Ç¤¤Þ¤¹¡£¤â¤·¡¢¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ò¹â¤¯¤·¤¹¤®¤ë¤È¡¢¥«¡¼¥Í¥ë¤Î¶¦Í¥á¥â¥ê¡¼¶õ´Ö¤ÎÀ©¸ÂÃÍ¤ò±Û¤¨¤Æ¤·¤Þ¤¦¤¿¤á¤Ë postmaster ¤¬Áö¤é¤Ê¤¯¤Ê¤ë¤Ç¤·¤ç¤¦¡£´ûÄêÃÍ¤Ç¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥Ð¥Ã¥Õ¥¡¤ÎÂç¤¤µ¤Ï 8K ¤Ç¡¢¥Ð¥Ã¥Õ¥¡¿ô¤Ï 1000 ¤Ç¤¹¡£
+
 
  sort_mem (PostgreSQL 8.0¤«¤é¤Ï: work_mem)¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢¤½¤ì¤¾¤ì¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¡¦¥×¥í¥»¥¹¤¬°ì»þÅª¤ÊÊÂ¤ÙÂØ¤¨¤Ë¤è¤Ã¤Æ»È¤¦¥á¥â¥ê¡¼¤ÎºÇÂç¥µ¥¤¥º¤òÁý¤ä¤¹¤³¤È¤â¤Ç¤¤Þ¤¹¡£ ´ûÄêÃÍ¤Ï 1024 (¤¹¤Ê¤ï¤Á¡¢1MB)¤Ç¤¹¡£
+
 
  ¤Þ¤¿¡¢CLUSTER ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¡¢¥Æ¡¼¥Ö¥ë¤Î¥Ç¡¼¥¿¤ò¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ë¹ç¤ï¤»¤ë¤¿¤á¤Ë¥°¥ë¡¼¥×²½¤¹¤ë¤³¤È¤â¤Ç¤¤Þ¤¹¡£¾Ü¤·¤¯¤Ï¡¢¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç CLUSTER ¤ò¸«¤Æ²¼¤µ¤¤¡£
+
 
-
 
3.7)	¤É¤Î¤è¤¦¤Ê¥Ç¥Ð¥°µ¡Ç½¤¬»È¤¨¤Þ¤¹¤«¡©
 
  PostgreSQL ¤Ï¡¢¥Ç¥Ð¥°¤Î¤¿¤á¤Ë°ÕÌ£¤Î¤¢¤ë¡¢¾õÂÖ¾ðÊó¤òÊó¹ð¤¹¤ë¤¤¤¯¤Ä¤«¤Îµ¡Ç½¤ò»ý¤Á¤Þ¤¹¡£
+
 
  ¤Þ¤º¡¢--enable-cassert ¥ª¥×¥·¥ç¥ó¤Ç configure ¤òÁö¤é¤»¤Þ¤¹¡£¤½¤¦¤·¤Æ¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢Âô»³¤Î assert() ¤¬¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¤Î¿ÊÄ½¾õ¶·¤ò´Æ»ë¤·¡¢²¿¤«Í½´ü¤»¤Ì¤³¤È¤¬µ¯¤¤ë¤È¥×¥í¥°¥é¥à¤òÄä»ß¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
+
 
  postmaster ¤È postgres ¤ÎÎ¾Êý¤Ç¤¤¤¯¤Ä¤«¤Î¥Ç¥Ð¥°¡¦¥ª¥×¥·¥ç¥ó¤ÎÍøÍÑ¤¬¤Ç¤¤Þ¤¹¡£¤Þ¤º¡¢¼¡¤Î¤è¤¦¤Ë  postmaster ¤òµ¯Æ°¤¹¤ë¤È¤¤Ï¤¤¤Ä¤Ç¤â¡¢É¸½à½ÐÎÏ¤È¥¨¥é¡¼½ÐÎÏ¤ò¥í¥°¡¦¥Õ¥¡¥¤¥ë¤ËÁ÷¤ë¤è¤¦¤Ë¤·¤Æ¤¢¤ë¤³¤È¤ò³Î¤«¤á¤Æ²¼¤µ¤¤¡£
+
 
  	cd /usr/local/pgsql
-	./bin/postmaster >server.log 2>&1 &
+	./bin/postmaster >server.log 2>&1 &
 
 
  ¤³¤ì¤Ë¤è¤ê PostgreSQL ¤ÎºÇ¾åÉô¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë server.log ¥Õ¥¡¥¤¥ë¤¬ÃÖ¤«¤ì¤Þ¤¹¡£¤³¤Î¥Õ¥¡¥¤¥ë¤Ï¥µ¡¼¥Ð¡¼¤¬Áø¶ø¤·¤¿ÌäÂê¤ä¥¨¥é¡¼¤Ë¤Ä¤¤¤ÆÍÍÑ¤Ê¾ðÊó¤ò´Þ¤ß¤Þ¤¹¡£Postmaster ¤Ï¹¹¤Ë¾ÜºÙ¤Ê¾ðÊó¤òÊó¹ð¤¹¤ë¤¿¤á¤Î -d ¥ª¥×¥·¥ç¥ó¤ò»ý¤Á¤Þ¤¹¡£¤½¤Î -d ¥ª¥×¥·¥ç¥ó¤Ï¡¢¥Ç¥Ð¥°¡¦¥ì¥Ù¥ë¤ò»ØÄê¤·¤Þ¤¹¡£¹â¤¤¥Ç¥Ð¥°¡¦¥ì¥Ù¥ë¤Ç¤Ï¡¢Âç¤¤Ê¥í¥°¥Õ¥¡¥¤¥ë¤òÀ¸À®¤¹¤ë¤³¤È¤ËÃí°Õ¤·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
+
 
 ¤â¤·¡¢postmaster¤¬Áö¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢postgres¥Ð¥Ã¥¯¥¨¥ó¥É¤ò¥³¥Þ¥ó¥É¥é¥¤¥ó¤«¤éÁö¤é¤»¤ë¤³¤È¤¬¤Ç¤¡¢Ä¾ÀÜSQLÊ¸¤ò¥¿¥¤¥×¤¹¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£¤³¤Î¤ä¤ê¤«¤¿¤Ï¡¢¥Ç¥Ð¥°ÌÜÅª¤Î¤È¤¤À¤±¤ª¾©¤á¤·¤Þ¤¹¡£¥»¥ß¥³¥í¥ó¤Ç¤Ï¤Ê¤¯¡¢²þ¹Ô¤¬Ìä¤¤¹ç¤ï¤»¤Î½ª¤ê¤Ë¤Ê¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤â¤·¡¢¥Ç¥Ð¥°¥·¥ó¥Ü¥ë¤òÆþ¤ì¤Æ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤¤¤ì¤Ð¡¢¥Ç¥Ð¥Ã¥¬¤ò»È¤Ã¤Æ²¿¤¬µ¯¤¤Æ¤¤¤ë¤«¤ò¸«¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£postmaster ¤«¤é¥Ð¥Ã¥¯¥¨¥ó¥É¤ò³«»Ï¤·¤¿¤ï¤±¤Ç¤Ï¤Ê¤¤¤Î¤Ç¡¢ÆÈÎ©¤Ê´Ä¶¤ÇÁö¤Ã¤Æ¤¤¤ë¤Î¤Ç¤Ï¤Ê¤¯¥í¥Ã¥¯¡¿¥Ð¥Ã¥¯¥¨¥ó¥É¤È¤ÎÂÐÏÃ¤ÎÌäÂê¤¬½ÅÊ£¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
+
 
-	 ¤â¤·¡¢postmaster¤¬Áö¤Ã¤Æ¤¤¤ì¤Ð¡¢¤¢¤ë¥¦¥£¥ó¥É¥¦¤Çpsql¤ò³«»Ï¤¹¤ë¤È¡¢
SELECT pg_backend_pid()
¤ò»È¤Ã¤Æ¡¢psql ¤Ç»È¤ï¤ì¤ë postgres ¥×¥í¥»¥¹¤ÎPID¤¬¸«¤Ä¤«¤ê¤Þ¤¹¡£
+	 ¤â¤·¡¢postmaster¤¬Áö¤Ã¤Æ¤¤¤ì¤Ð¡¢¤¢¤ë¥¦¥£¥ó¥É¥¦¤Çpsql¤ò³«»Ï¤¹¤ë¤È¡¢SELECT pg_backend_pid()¤ò»È¤Ã¤Æ¡¢psql ¤Ç»È¤ï¤ì¤ë postgres ¥×¥í¥»¥¹¤ÎPID¤¬¸«¤Ä¤«¤ê¤Þ¤¹¡£
 ¥Ç¥Ð¥Ã¥¬¤ò»È¤Ã¤Æpostgres¤ÎPID¤Ë¥¢¥¿¥Ã¥Á(attach)¤·¤Þ¤¹¡£¥Ç¥Ð¥Ã¥¬¤ÎÃæ¤«¤é¥Ö¥ì¡¼¥¯¡¦¥Ý¥¤¥ó¥È¤ò¥»¥Ã¥È¤·¡¢psql ¤«¤éÌä¤¤¹ç¤ï¤»¤òÈ¯¹Ô¤·¤Þ¤¹¡£¥Ç¥Ð¥°¤Î¤¿¤á¤Ëpostgres¤ò»ÏÆ°¤¹¤ë¾ì¹ç¤Ï¡¢PGOPTIONS="-W n" ¤òÀßÄê¤Ç¤¡¢¤½¤ì¤«¤é¡¢psql ¤ò³«»Ï¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢n ÉÃ³«»Ï¤òÃÙ¤é¤»¤ë¤Ï¤º¤Ê¤Î¤Ç¡¢¥Ç¥Ð¥Ã¥¬¤Ç¥×¥í¥»¥¹¤Ë¥¢¥¿¥Ã¥Á¤·¤Æ¡¢¥Ö¥ì¡¼¥¯¥Ý¥¤¥ó¥È¤òÀßÄê¤·¡¢³«»Ï¤«¤é½ç¤òÄÉ¤Ã¤Æ¸«¤Æ¤æ¤¯¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
-
 ¤¤¤¯¤Ä¤«¤Î
log_*¥µ¡¼¥Ð¹½À®ÊÑ¿ô¤Ï¡¢¥Ç¥Ð¥Ã¥°¤ÈÀÇ½Â¬Äê¤Ë¤È¤Æ¤âÌò¤ËÎ©¤Ä¥×¥í¥»¥¹¤ÎÅý·×¤Î°õºþ¤ò²ÄÇ½¤Ë¤·¤Þ¤¹¡£
+
+ ¤¤¤¯¤Ä¤«¤Îlog_*¥µ¡¼¥Ð¹½À®ÊÑ¿ô¤Ï¡¢¥Ç¥Ð¥Ã¥°¤ÈÀÇ½Â¬Äê¤Ë¤È¤Æ¤âÌò¤ËÎ©¤Ä¥×¥í¥»¥¹¤ÎÅý·×¤Î°õºþ¤ò²ÄÇ½¤Ë¤·¤Þ¤¹¡£
+
 
  ²¿¤È¤¤¤¦´Ø¿ô¤¬¤É¤Î¤¯¤é¤¤¼Â¹Ô»þ´Ö¤ò¿©¤Ã¤Æ¤¤¤ë¤«¤ò¸«¤ë¤¿¤á¤Ë¡¢¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°¡Ê¥×¥í¥Õ¥£¡¼¥ëÉÕ¤¡Ë¤Ç¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤³¤È¤â²ÄÇ½¤Ç¤¹¡£¤½¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¤Î¥×¥í¥Õ¥£¡¼¥ë¡¦¥Õ¥¡¥¤¥ë¤Ï pgsql/data/base/dbname ¥Ç¥£¥ì¥¯¥È¥ê¤Ë³ÊÇ¼¤µ¤ì¤ë¤Ç¤·¤ç¤¦¡£¥¯¥é¥¤¥¢¥ó¥È¤Î¥×¥í¥Õ¥£¡¼¥ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î¸½¹Ô¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¤ë¤Ç¤·¤ç¤¦¡£Linux ¤Ç¤Þ¤È¤â¤Ê¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°¤ò¹Ô¤¦¤Ë¤Ï -DLINUX_PROFILE ¤Ç¥³¥ó¥Ñ¥¤¥ë¤¹¤ëÉ¬Í×¤¬¤¢¤ê¤Þ¤¹¡£
+
 
-
-
 
3.8)	ÀÜÂ³¤·¤è¤¦¤È¤¹¤ë¤È¤¤Ë 'Sorry, too many clients' ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
 
 
  postmaster¤¬Æ±»þ»ÏÆ°¤Ç¤¤ë¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹¤ËÂÐ¤¹¤ëÀ©¸Â¿ô¤òÁý¤ä¤¹É¬Í×¤¬¤¢¤ê¤Þ¤¹¡£
+
 ´ûÄê¤ÎºÇÂç¥×¥í¥»¥¹¤Ï32¥×¥í¥»¥¹¤Ç¤¹¡£-N¤ËÅ¬ÀÚ¤ÊÃÍ¤ò°ú¿ô¤Ë¤·¤Æpostmaster¤òºÆµ¯Æ°¤¹¤ë¤«¡¢PostgreSQL.conf ¤ò½¤Àµ¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢¤½¤ÎÃÍ¤òÁý¤ä¤¹¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
+
 
 ¤â¤·¡¢-N ¤ò 32¤è¤ê¤âÂç¤¤¯¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢-B¤â´ûÄê¤Î64¤è¤êÂç¤¤¤ÃÍ¤ËÁý²Ã¤µ¤»¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¤·¡¢-B ¤Ï¾¯¤Ê¤¯¤È¤â -N ¤Î2ÇÜ¤Ï¤Ê¤¯¤Æ¤Ï¤Ê¤é¤º¡¢¤ª¤½¤é¤¯ºÇ¹âÀÇ½¤òË¾¤à¤Ê¤é¤Ð¤½¤ì¤è¤êÂç¤¤¤ÃÍ¤¬É¬Í×¤Ê¤Ï¤º¤Ç¤¹¡£¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹¤ò¤¿¤¯¤µ¤ó¤Ë¤¹¤ë¤È¡¢¤¤¤í¤¤¤í¤ÊUnix¥«¡¼¥Í¥ë¹½À®¥Ñ¥é¥á¡¼¥¿¤âÁý¤ä¤¹¤³¤È¤¬É¬Í×¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
 ¶¦Í¥á¥â¥ê¡¼¡¦¥Ö¥í¥Ã¥¯¤ÎºÇÂçÃÍ(SHMMAX)¡¢
@@ -767,17 +773,19 @@ PostgreSQL Administrator's Guide 
 ¤â³ÎÇ§»ö¹à¤Ë´Þ¤Þ¤ì¤Þ¤¹¡£
 PostgreSQL¤Ëµö¤µ¤ì¤ë¥Ð¥Ã¥¯¥¨¥ó¥É¤Î¥×¥í¥»¥¹¿ô¤¬À©¸Â¤µ¤ì¤Æ¤¤¤ë¤Î¤Ï¡¢
 ¥·¥¹¥Æ¥à¤Î¥ê¥½¡¼¥¹¤ò»È¤¤²Ì¤·¤Æ¤·¤Þ¤¦¤³¤È¤òÈò¤±¤ë¤¿¤á¤Ç¤¹¡£
+
 
-
-
3.9)	pgsql_tmp ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤Ë¤Ï²¿¤¬¤¢¤ê¤Þ¤¹¤«¡©
+
3.9)	pgsql_tmp ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤Ë¤Ï²¿¤¬¤¢¤ê¤Þ¤¹¤«¡©
 
 
  Ìä¤¤¹ç¤ï¤»¼Â¹Ô¥â¥¸¥å¡¼¥ë¤Ë¤è¤Ã¤ÆÀ¸À®¤µ¤ì¤¿°ì»þÅª¤Ê¥Õ¥¡¥¤¥ë¤¬¡¢¤³¤Î¥Ç¥£
 ¥ì¥¯¥È¥ê¤Ë´Þ¤Þ¤ì¤Þ¤¹¡£Îã¤¨¤Ð¡¢¤â¤· ORDER BY ¶ç¤òËþ¤¿¤¹¤¿¤á¤Ë¥Ð¥Ã¥¯¥¨¥ó¥É¤Î -S ¥Ñ¥é¥á¡¼¥¿¤Çµö²Ä¤·¤¿ÃÍ¤è¤ê¤âÂç¤¤Ê¥¹¥Ú¡¼¥¹¤¬¥½¡¼¥È¤ÎºÝ¤ËÉ¬Í×¤À¤È¤¹¤ë¤È¡¢°î¤ì¤¿¥Ç¡¼¥¿¤òÊÝ»ý¤¹¤ë¤¿¤á¤Ë°ì»þÅª¤Ê¥Õ¥¡¥¤¥ë¤¬¤¤¤¯¤Ä¤«¤³¤³¤ËÀ¸À®¤µ¤ì¤Þ¤¹¡£
+
 
 °ì»þÅª¤Ê¥Õ¥¡¥¤¥ë¤Ï¼«Æ°Åª¤Ë¾Ã¤·µî¤é¤ì¤ë¤Ï¤º¤Ç¤¹¤¬¡¢¤â¤·¡¢¥½¡¼¥È¤ÎÅÓÃæ¤Ç¥Ð¥Ã¥¯¥¨¥ó¥É¤¬¥¯¥é¥Ã¥·¥å¤·¤Æ¤·¤Þ¤¦¤È¤½¤¦¤Ï¤Ê¤ê¤Þ¤»¤ó¡£postmaster¤ÎÄä»ß¤È¥ê¥¹¥¿¡¼¥È¤Ç¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¾Ã¤·¤µ¤é¤ì¤Þ¤¹¡£
+
 
-+     [ÌõÃí¡§
 	 SYSLOGD ·ÐÍ³¤Ç¥í¥°¤ò½ÐÎÏ¤¹¤ë¤Ë¤Ï¡¢¤Þ¤º¡¢configure ¤ò --enable-syslog 
 	ÉÕ¤¤ÇÁö¤é¤»¤¿¸å¡¢¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£
@@ -787,41 +795,40 @@ PostgreSQL
 	¥ª¥×¥·¥ç¥óÉÕ¤¤Ë¤Æ¥µ¡¼¥Ð¥â¡¼¥É¤Çµ¯Æ°¤·¤Þ¤¹¡£(¥Ð¡¼¥¸¥ç¥ó 7.1 ¤«¤é¤Ï 
 	pg_options ¤Ï PostgreSQL.conf ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£)
     ]
-
+
 
-
 
3.10)  PostgreSQL¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤ò¥¢¥Ã¥×¥Ç¡¼¥È¤¹¤ë¤Î¤Ë¥À¥ó¥×¤È¥ê¥¹¥È¥¢¤ò¤·¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
 
 PostgreSQL¥Á¡¼¥à¤Ï¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ç¤Ï¾®¤µ¤ÊÊÑ¹¹¤·¤«¹Ô¤Ê¤¤¤Þ¤»¤ó¤Î¤Ç¡¢7.2 ¤«¤é 7.2.1 ¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¤Ï¥À¥ó¥×¤È¥ê¥¹¥È¥¢¤ÎÉ¬Í×¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤·¤«¤·¡¢¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹(¤¿¤È¤¨¤Ð¡¢7.2¤«¤é7.3¤Ø¤Î¤è¤¦¤Ê)¤Ç¤Ï¡¢¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ë¤ä¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤ÎÆâÉô¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÊÑ¹¹¤ò¤·¤Ð¤·¤Ð¹Ô¤Ê¤¤¤Þ¤¹¡£¤³¤ì¤é¤ÎÊÑ¹¹¤Ï¤¿¤¤¤Æ¤¤Ê£»¨¤Ç¡¢¤½¤Î¤¿¤á²æ¡¹¤Ï¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤Î¤¿¤á¤Î¸åÊý¸ß´¹À¤ò°Ý»ý¤¹¤ë¤³¤È¤¬¤Ç¤¤Þ¤»¤ó¡£¥À¥ó¥×¤ÏÈÆÍÑ¥Õ¥©¡¼¥Þ¥Ã¥È¤Ç¥Ç¡¼¥¿¤ò½ÐÎÏ¤·¡¢¤½¤ì¤ò¿·¤·¤¤ÆâÉô¥Õ¥©¡¼¥Þ¥Ã¥È¤ËÆÉ¤ß¹þ¤à¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
 
 ¥Ç¥£¥¹¥¯¾å¤Ç¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤ËÊÑ¹¹¤Î¤Ê¤¤Æ±°ì¥ê¥ê¡¼¥¹¤Ç¤Ï¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ï¡¢¥À¥ó¥×¡¿¥ê¥¹¥È¥¢¤Ç¤Ï¤Ê¤¯¡¢pg_upgrade ¥¹¥¯¥ê¥×¥È¤ò»È¤¦¤³¤È¤¬¤Ç¤¤Þ¤¹¡£¥ê¥ê¡¼¥¹¥Î¡¼¥È¤Ë¤Ï¡¢pg_upgrade ¤¬ÍøÍÑ²ÄÇ½¤Ê¥ê¥ê¡¼¥¹¤«¤É¤¦¤«µ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
 
-
 
3.11) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤ó¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©
 
 PC¥Ï¡¼¥É¥¦¥§¥¢¤Ï¤Û¤È¤ó¤É¸ß´¹À¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢¤Û¤È¤ó¤É¤Î¿Í¤Ï¡¢¤¹¤Ù¤Æ¤ÎPC¥Ï¡¼¥É¥¦¥§¥¢¤¬Æ±¤¸ÉÊ¼Á¤À¤È»×¤¤¹þ¤à·¹¸þ¤¬¤¢¤ê¤Þ¤¹¡£¤·¤«¤·¡¢¤½¤ì¤Ï´Ö°ã¤¤¤Ç¤¹¡£ECC RAM¡¢SCSI¡¢¤ª¤è¤Ó¡¢¹âÉÊ¼Á¥Þ¥¶¡¼¥Ü¡¼¥É¤Ï¡¢°Â¤¤¥Ï¡¼¥É¥¦¥§¥¢¤ËÈæ¤Ù¤ë¤È¡¢¤è¤ê¿®ÍêÀ¤¬¹â¤¯¡¢¤è¤êÀÇ½¤âÎÉ¤¤¤Î¤Ç¤¹¡£PostgreSQL ¤Ï¤Û¤È¤ó¤É¤Î¥Ï¡¼¥É¥¦¥§¥¢¤Ç²ÔÆ¯¤·¤Þ¤¹¤¬¡¢¿®ÍêÀ¤äÀÇ½¤¬½ÅÍ×¤Ê¾ì¹ç¤Ï¡¢¥Ï¡¼¥É¥¦¥§¥¢¤Î¥ª¥×¥·¥ç¥ó¤ò¸¦µæ¤¹¤ë¤³¤È¤¬¸ÌÀ¤Ç¤¹¡£¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ç¤â¥Ï¡¼¥É¥¦¥§¥¢¥ª¥×¥·¥ç¥ó¤È¥È¥ì¡¼¥É¥ª¥Õ¤Ë¤Ä¤¤¤ÆµÄÏÀ¤¹¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
 
 
-
 

 Áàºî¾å¤Î¼ÁÌä
-
 
 
4.1)	¥Ð¥¤¥Ê¥ê¡¦¥«¡¼¥½¥ë¤ÈÄÌ¾ï¥«¡¼¥½¥ë¤È¤Î¸·Ì©¤Ê°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©
 
 
  ¾Ü½Ò¤Ï¡¢¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç DECLARE ¤ò¸«¤Æ²¼¤µ¤¤¡£
+
 
-
 
4.2)	ºÇ½é¤Î¿ô¥í¥¦¤Î¤ß¤ò SELECT¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©¥é¥ó¥À¥à¤Ê¥í¥¦¡©
 
 
  ¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤ÇFETCH¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£¤¢¤ë¤¤¤Ï¡¢SELECT ... LIMIT....¤ò»È¤Ã¤Æ¤ß¤Æ²¼¤µ¤¤¡£
+
 
 ¤¿¤È¤¨¡¢Íß¤·¤¤¤Î¤ÏºÇ½é¤Î¿ô¥í¥¦¤À¤±¤Ç¤â¡¢¤¹¤Ù¤Æ¤ÎÌä¤¤¹ç¤ï¤»¤òÉ¾²Á¤·¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£ORDER BY ¤ò»ý¤Ã¤¿Ìä¤¤¹ç¤ï¤»¤ò»È¤¦¤³¤È¤ò¹Í¤¨¤Æ¤ß¤Æ²¼¤µ¤¤¡£
 ¤â¤·¡¢ORDER BY¤Ë¹ç¤Ã¤¿¥¤¥ó¥Ç¥Ã¥¯¥¹¤¬¤¢¤ë¤È¤¹¤ë¤È PostgreSQL¤ÏÍ×µá¤µ¤ì¤¿ºÇ½é¤Î¿ô¥í¥¦¤À¤±¤ÇÉ¾²Á¤Ç¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢¤Ç¤Ê¤ì¤Ð¡¢PostgreSQL ¤Ï°Õ¿Þ¤·¤¿¥í¥¦¤¬À¸À®¤µ¤ì¤ë¤Þ¤Ç¤¹¤Ù¤Æ¤Î¥í¥¦¤òÉ¾²Á¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
+
 
    ¥é¥ó¥À¥à¤Ê¥í¥¦¤òSELECT¤¹¤ë¤Ë¤Ï¡¢¼¡¤ÎÊ¸¤ò»È¤¤¤Þ¤¹¡§ 
+
      SELECT col
     FROM tab
@@ -829,7 +836,6 @@ PC
     LIMIT 1;
 
 
-
 
4.3)	¥Æ¡¼¥Ö¥ë¤ä¤½¤ÎÂ¾¤Î¾ðÊó¤Î¥ê¥¹¥È¤ò psql ¤Ç¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
 
 
@@ -842,6 +848,7 @@ PC
 
 
 DROP COLUMNµ¡Ç½¤¬¡¢ALTER TABLE DROP COLUMN ¤È¤·¤Æ¥ê¥ê¡¼¥¹7.3
 ¤Ë²Ã¤¨¤é¤ì¤Þ¤·¤¿¡£¤½¤ì¤Þ¤Ç¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢¤½¤ÎÂå¤ï¤ê¤Ë¤³¤¦¤·¤Þ¤¹:
+
 
  	BEGIN;
@@ -855,6 +862,7 @@ PC
 
 
 ¥«¥é¥à¤Î¥Ç¡¼¥¿¥¿¥¤¥×¤Ï¼¡¤ÎÊ¸¤ÇÊÑ¤¨¤é¤ì¤Þ¤¹¡§ 
+
 
      BEGIN;
@@ -865,12 +873,13 @@ PC
 
 
 ¤³¤ì¤ò¹Ô¤Ê¤Ã¤¿¤È¤¤Ï¡¢Ëõ¾Ã¤µ¤ì¤¿¹Ô¤¬»È¤Ã¤Æ¤¤¤ë¥Ç¥£¥¹¥¯¶õ´Ö¤ò²ó¼ý¤¹¤ë¤¿¤á¤ËVACUUM FULL tab¤ò¤·¤¿¤Û¤¦¤¬ÎÉ¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
+
 
-
 
4.5)	¥í¥¦¡¢¥Æ¡¼¥Ö¥ë¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎºÇÂç¥µ¥¤¥º¤Ï¡©
 
 
  À©¸Â¤Ï°Ê²¼¤Î¤È¤ª¤ê¤Ç¤¹¡£
+
  ¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎºÇÂç¥µ¥¤¥º? 	À©¸ÂÌµ¤· (32 TB ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤âÂ¸ºß¤·¤Þ¤¹)
 ¥Æ¡¼¥Ö¥ë¤ÎºÇÂç¥µ¥¤¥º?           32TB
@@ -882,22 +891,25 @@ PC
 
 
  ¤â¤Á¤í¤ó¡¢¤³¤ì¤é¤Ï¼ÂºÝ¤ÏÌµÀ©¸Â¤Ç¤Ï¤Ê¤¯¡¢¥Ç¥£¥¹¥¯ÍÆÎÌ¤È¥á¥â¥ê¡¼¤ä¥¹¥ï¥Ã¥×¥¹¥Ú¡¼¥¹¤ÎÂç¤¤µ¤Ë¤è¤êÀ©¸Â¤µ¤ì¤Þ¤¹¡£ÀÇ½¤Ï¤³¤ì¤é¤ÎÃÍ¤¬¤³¤È¤Î¤Û¤«Âç¤¤Ê»þ¤ËÀú¤ê¤ò¼õ¤±¤Þ¤¹¡£
+
 
  ºÇÂç¥Æ¡¼¥Ö¥ë¥µ¥¤¥º¤Î32TB¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ë¤è¤ëµðÂç¥Õ¥¡¥¤¥ë¤Î¥µ¥Ý¡¼¥È¤ÏÉ¬Í×¤È¤·¤Þ¤»¤ó¡£µðÂç¤Ê¥Æ¡¼¥Ö¥ë¤ÏÊ£¿ô¤Î1GB¤Î¥Õ¥¡¥¤¥ë¤ËÊ¬¤±¤ÆÊÝÂ¸¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÀ©¸Â¤Ï½ÅÍ×¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
+
 
  ¥Ç¥Õ¥©¥ë¥È¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò32k¤Ë¤¹¤ë¤³¤È¤Ç¡¢ºÇÂç¥Æ¡¼¥Ö¥ë¥µ¥¤¥º¤ÈºÇÂç¥«¥é¥à¿ô¤È¤ò£´ÇÜ¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
+
 
 
-
 
4.6)	°ìÈÌÅª¤Ê¥Æ¥¥¹¥È¥Õ¥¡¥¤¥ë¤«¤é¥Ç¡¼¥¿¤òÊÝÂ¸¤¹¤ë¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯ÍÆÎÌ¤Ï¤É¤Î¤¯¤é¤¤É¬Í×¤Ç¤¹¡©
 
-
-ÉáÄÌ¤Î¥Æ¥¥¹¥È¥Õ¥¡¥¤¥ë¤ò PostgreSQL ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÊÝÂ¸¤¹¤ë¤Ë¤Ï¡¢ºÇÂç¤ÇÌó5ÇÜ¤Î¥Ç¥£¥¹¥¯ÍÆÎÌ¤òÉ¬Í×¤È¤·¤Þ¤¹¡£
+

+ÉáÄÌ¤Î¥Æ¥¥¹¥È¥Õ¥¡¥¤¥ë¤ò PostgreSQL ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÊÝÂ¸¤¹¤ë¤Ë¤Ï¡¢ºÇÂç¤ÇÌó5ÇÜ¤Î¥Ç¥£¥¹¥¯ÍÆÎÌ¤òÉ¬Í×¤È¤·¤Þ¤¹¡£
 
  ÎãÂê¤È¤·¤Æ¡¢³Æ¹Ô¤ËÀ°¿ô¤È¥Æ¥¥¹¥Èµ½Ò¤ò»ý¤Ä 100,000¹Ô¤Î¥Õ¥¡¥¤¥ë¤ò¹Í¤¨
 ¤Æ¤ß¤Þ¤·¤ç¤¦¡£¥Æ¥¥¹¥È¤ÎÊ¸»úÎó¤ÎÊ¿¶ÑÄ¹¤µ¤ò20¥Ð¥¤¥È¤È²¾Äê¤¹¤ë¤È¡¢¥Õ¥é¥Ã¥È
 ¥Õ¥¡¥¤¥ë¤ÎÂç¤¤µ¤ÏÌó2.8MB ¤Ç¤¹¡£¤³¤Î¥Ç¡¼¥¿¤ò´Þ¤à PostgreSQL ¥Ç¡¼¥¿¥Ù¡¼¥¹
 ¥Õ¥¡¥¤¥ë¤ÎÂç¤¤µ¤Ï¼¡¤Î¤è¤¦¤ËÌó6.4MB¤È¸«ÀÑ¤â¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡§
+
 
      32 bytes: ³Æ¥í¥¦¤Î¥Ø¥Ã¥À(³µ»»)
@@ -921,26 +933,29 @@ PC
 
 
 ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢¤³¤ì¤Û¤É¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤ÏÍ×µá¤·¤Þ¤»¤ó¤¬¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹ÉÕ¤±¤µ¤ì¤ë¥Ç¡¼¥¿¤ò´Þ¤à°Ê¾å¡¢¤½¤ì¤Ê¤ê¤ËÂç¤¤¯¤Ê¤ê¤Þ¤¹¡£
+
 NULL¤Ï¥Ó¥Ã¥È¥Þ¥Ã¥×¤È¤·¤ÆÊÝÂ¸¤µ¤ì¤Æ¤¤¤Æ¡¢¤½¤ì¤é¤¬¤ï¤º¤«¤Ë¥¹¥Ú¡¼¥¹¤ò»È¤¤¤Þ¤¹¡£
+
 
-
-
 
4.7)	ÄêµÁ¤µ¤ì¤¿¥Æ¡¼¥Ö¥ë¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¢¤ª¤è¤Ó¡¢¥æ¡¼¥¶¤ò¤É¤Î¤è¤¦¤Ë¤·¤Æ¸«¤Ä¤±½Ð¤·¤Þ¤¹¤«¡©
 
 
  psql ¤Ë¤Ï¤¤¤í¤¤¤í¤Ê¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¡¦¥³¥Þ¥ó¥É¤¬¤¢¤ê¡¢¤³¤¦¤·¤¿¾ðÊó¤òÉ½¼¨¤·¤Þ¤¹¡£¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¡¦¥³¥Þ¥ó¥É¤Î¼ïÎà¤ò¸«¤ë¤Ë¤Ï \? ¤ò»È¤Ã¤Æ²¼¤µ¤¤¡£¤Þ¤¿¡¢pg_ ¤Ç»Ï¤Þ¤ë¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ë¤Ë¤âµ½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤µ¤é¤Ë¡¢psql -l ¤Ï¤¹¤Ù¤Æ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò¥ê¥¹¥ÈÉ½¼¨¤·¤Þ¤¹¡£
+
 
  ¤Þ¤¿¡¢pgsql/src/tutorial/syscat.source ¥Õ¥¡¥¤¥ë¤òÁö¤é¤»¤Æ¤ß¤Æ²¼¤µ¤¤¡£¤½¤ì¤Ï¡¢Âô»³¤Î SELECT Ê¸¤Ë¤è¤êÉ¬Í×¤Ê¾ðÊó¤ò¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥·¥¹¥Æ¥à¡¦¥Æ¡¼¥Ö¥ë¤«¤é¼è¤ê½Ð¤·¤ÆÎã¼¨¤·¤Æ¤¯¤ì¤Þ¤¹¡£
+
 
-
 
4.8)	Ìä¤¤¹ç¤ï¤»¤¬ÃÙ¤¤¤¦¤¨¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤Ã¤Æ¤¤¤ëÍÍ»Ò¤¬¤¢¤ê¤Þ¤»¤ó¡£¤Ê¤¼¤Ç¤¹¤«¡©
 
 
+
 ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¼«Æ°Åª¤Ë¤¹¤Ù¤Æ¤ÎÌä¤¤¹ç¤ï¤»¤Ç»È¤ï¤ì¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¥Æ¡¼
 ¥Ö¥ë¤¬ºÇ¾®¥µ¥¤¥º¤è¤êÂç¤¤¯¡¢Ìä¤¤¹ç¤ï¤»¤Ç¤½¤Î¤ï¤º¤«¤Ê¥Ñ¡¼¥»¥ó¥Æ¡¼¥¸¤Î¥í¥¦¤ò
 ÁªÂò¤¹¤ë»þ¤À¤±¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï»È¤ï¤ì¤Þ¤¹¡£¤³¤ì¤Ï¥¤¥ó¥Ç¥Ã¥¯¥¹¥¹¥¥ã¥ó¤Ë¤è
 ¤êµ¯¤³¤µ¤ì¤ë¥é¥ó¥À¥à¤Ê¥Ç¥£¥¹¥¯¥¢¥¯¥»¥¹¤Ï¡¢¥Æ¡¼¥Ö¥ë¤ò¥¹¥È¥ì¡¼¥È¤ËÆÉ¤à½ç¼¡
 Áöºº¤è¤ê¤âÃÙ¤¯¤Ê¤ë¤³¤È¤¬¤¢¤ë¤«¤é¤Ç¤¹¡£
+
 
     ¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¦¤«¤ò·èÄê¤¹¤ë¤¿¤á¤Ë¡¢PostgreSQL ¤Ï¥Æ¡¼¥Ö¥ë¤Ë¤Ä¤¤
 ¤Æ¤ÎÅý·×¾ðÊó¤ò»ý¤¿¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤³¤ÎÅý·×¾ðÊó¤Ï¡¢VACUUM
@@ -953,10 +968,12 @@ ANALYZE
     
 ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢ÄÌ¾ï ORDER BY ¤ä·ë¹ç¤ò¹Ô¤Ê
 ¤¦¤¿¤á¤Ë¤Ï»È¤ï¤ì¤Þ¤»¤ó¡£½ç¼¡¥¹¥¥ã¥ó¤ËÂ³¤¯ÌÀ¼¨Åª¥½¡¼¥È¤Ï¡¢µðÂç¤Ê¥Æ¡¼¥Ö¥ë
 ¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¥¹¥¥ã¥ó¤è¤ê¤âÉáÄÌ¤Ï¹âÂ®¤Ç¤¹¡£
+
     ¤·¤«¤·¡¢ORDER BY¤ÈÁÈ¤ß¹ç¤ï¤µ¤ì¤¿LIMIT 
 ¤Ï¡¢¥Æ¡¼¥Ö¥ë¤Î¾®¤µ¤ÊÉôÊ¬¤òÊÖ¤¹¤¿¤á¤Ë¤¿¤Ó¤¿¤Ó¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¦¤Ç¤·¤ç¤¦¡£
 ¼ÂºÝ¡¢MAX() ¤ä MIN() ¤¬¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤ï¤Ê¤¤¤È¤·¤Æ¤â¡¢¤³¤Î¤è¤¦¤ÊÃÍ¤ò
 ORDER BY ¤È LIMIT ¤ò»È¤Ã¤Æ¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤Ã¤Æ¼è¤ê½Ð¤¹¤³¤È¤¬²ÄÇ½¤Ç¤¹:
+
 
      SELECT col
@@ -969,23 +986,23 @@ ORDER BY 
 
      LIKE ¤¢¤ë¤¤¤Ï ~ ¤Î¤è¤¦¤Ê¥ï¥¤¥ë¥É¥«¡¼¥É±é»»
 »Ò¤ÏÆÃÊÌ¤Ê´Ä¶¤Ç¤·¤«»È¤¨¤Þ¤»¤ó¡§
+
     
-    ¸¡º÷Ê¸»úÎó¤¬Ê¸»úÎó¤ÎºÇ½é¤Ë¤¤¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡§
+    ¸¡º÷Ê¸»úÎó¤¬Ê¸»úÎó¤ÎºÇ½é¤Ë¤¤¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡§
     
     LIKE ¥Ñ¥¿¡¼¥ó¤¬%¤Ç»Ï¤Þ¤é¤Ê¤¤
     ~ (Àµµ¬É½¸½) ¥Ñ¥¿¡¼¥ó¤Ï^¤Ç»Ï¤Þ¤é¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤
-    
+    
     ¸¡º÷Ê¸»úÎó¤òÊ¸»ú¥¯¥é¥¹¤«¤é»Ï¤á¤ë¤³¤È¤Ï¤Ç¤¤Þ¤»¤ó¡£¤¿¤È¤¨¤Ð¡¢[a-e]¡£
     ILIKE ¤ä ~* ¤Î¤è¤¦¤ÊÂçÊ¸»ú¤È¾®Ê¸»ú¤ò¶èÊÌ¤·
 	¤Ê¤¤¸¡º÷¤Ï»È¤¨¤Þ¤»¤ó¡£¤½¤Î¤«¤ï¤ê¡¢¤³¤ÎFAQ¤Î4.12Àá¤ÇÀâÌÀ¤¹¤ë´Ø¿ô¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤¬»È¤¨¤Þ¤¹¡£
     initdb ¤Ë¤ª¤¤¤Æ¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤ÇC¥í¥±¡¼¥ë¤¬»È¤ï¤ì¤Ê
 ¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£¤½¤ÎÍýÍ³¤Ï¡¢C¥í¥±¡¼¥ë°Ê³°¤Ç¤Ï¼¡¤ËÂç¤¤ÊÊ¸»ú¤òÃÎ¤ë¤³¤È
-¤¬¤Ç¤¤Ê¤¤¤«¤é¤Ç¤¹¡£¤³¤Î¤è¤¦¤Ê¾ì¹ç¡¢LIKE¥¤¥ó¥Ç¥¯¥·¥ó¥°¤Ë¤À¤±
-Æ¯¤¯¤è¤¦¤Ê¡¢ÆÃÊÌ¤Êtext_pattern_ops¥¤¥ó¥Ç¥Ã¥¯¥¹¤òºîÀ®
+¤¬¤Ç¤¤Ê¤¤¤«¤é¤Ç¤¹¡£¤³¤Î¤è¤¦¤Ê¾ì¹ç¡¢LIKE¥¤¥ó¥Ç¥¯¥·¥ó¥°¤Ë¤À¤±
+Æ¯¤¯¤è¤¦¤Ê¡¢ÆÃÊÌ¤Êtext_pattern_ops¥¤¥ó¥Ç¥Ã¥¯¥¹¤òºîÀ®
 ¤¹¤ë¤³¤È¤â¤Ç¤¤Þ¤¹¡£
 
     
-    
 
     
8.0¤è¤êÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢¥Ç¡¼¥¿·¿¤¬¤Á¤ç¤¦¤É¥¤¥ó¥Ç¥Ã¥¯¥¹¤Î¥«¥é¥à¤Î·¿¤È°ìÃ×¤·¤Ê¤±¤ì¤Ð¡¢»È¤¨¤Ê¤¤¤³¤È¤¬¤·¤Ð¤·¤Ð¤¢¤ê¤Þ¤·¤¿¡£¤ª¤½¤é¤¯¡¢int2, int8, ¤ª¤è¤Ó numeric Åù¤Î¥«¥é¥à¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤¬¤½¤¦¤Ç¤¹¡£
 
@@ -994,84 +1011,84 @@ ORDER BY 
 ]
 
 
-
 
4.9)	Ìä¤¤¹ç¤ï¤»¥ª¥Ö¥Æ¥£¥Þ¥¤¥¶¤¬¤É¤Î¤è¤¦¤ËÌä¤¤¹ç¤ï¤»¤òÉ¾²Á¤¹¤ë¤Î¤«¤ò¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
 
 
  ¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç EXPLAIN ¤ò¸«¤Æ²¼¤µ¤¤¡£
+
 
-
 
4.10)	R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤È¤Ï²¿¤Ç¤¹¤«¡©
 
  R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¶õ´ÖÅª¤Ê¥Ç¡¼¥¿¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤òÉÕ¤±¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£¥Ï¥Ã¥·¥å¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤ÏÈÏ°Ï¤Î¸¡º÷¤¬¤Ç¤¤Þ¤»¤ó¡£¤Þ¤¿¡¢B-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤Ï¡¢£±¼¡¸µ¤Ç¤·¤«ÈÏ°Ï¤Î¸¡º÷¤¬¤Ç¤¤Þ¤»¤ó¡£R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤¢¤ì¤ÐÂ¿¼¡¸µ¤Î¥Ç¡¼¥¿¤ò°·¤¨¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢¤â¤· R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò point ·¿¤ÎÂ°À¤ËÉÕ¤±¤ë¤³¤È¤¬¤Ç¤¤ë¤È¤¹¤ë¤È¥·¥¹¥Æ¥à¤Ï¡¢¡ÖÄ¹Êý·Á¤Ë°Ï¤Þ¤ì¤¿ÅÀ¤ò¤¹¤Ù¤ÆÁªÂò¤¹¤ë¡×¤È¤¤¤¦¤è¤¦¤ÊÌä¤¤¹ç¤ï¤»¤Ë¡¢¤è¤ê¸úÎ¨ÎÉ¤¯Åú¤¨¤é¤ì¤Þ¤¹¡£
+
 
  R-Tree ¤ÎÀß·×¤Î¸¶Åµ¤È¤Ê¤ë¸¢°Ò¤¢¤ëÏÀÊ¸¤Ï:
+
 
  Guttman, A. "R-Trees: A Dynamic Index Structure for Spatial Searching."
 Proceedings of the 1984 ACM SIGMOD Int'l Conf on Mgmt of Data, 45-57.
+
 
  ¤³¤ÎÏÀÊ¸¤Ï¡¢Stonebraker ¶µ¼ø¤Î "Readings in Database Systems"
 ¤Ç¤â¼è¤ê¾å¤²¤é¤ì¤Æ¤¤¤Þ¤¹¡£
+
 
-
-
+     [ÌõÃí¡§
 	  ÆàÎÉÀèÃ¼Âç¤ÎÀÐÀî²Â¼£¤µ¤ó¤è¤êR-Tree´Ø·¸¤ÎÊ¸¸¥¤ò¾Ò²ð¤·¤ÆÄº¤¤Þ¤·¤¿¡£
 	ÆüËÜ¸ì Postgres ML ¤Î¥¢¡¼¥«¥¤¥Ö¤«¤é "Subject: [postgres95 801] spatial data structures" 
 		http://www.sra.co.jp/people/t-ishii/PostgreSQL/mhonarc/pgsql-jp/1996Oct/msg00007.html
 	¤ò¤´Í÷²¼¤µ¤¤¡£
     ]
-
+
 
  ÁÈ¹þ¤ß¤Î R-Tree ¤Ç¥Ý¥ê¥´¥ó¤ä¥Ü¥Ã¥¯¥¹¤òÁàºî¤Ç¤¤Þ¤¹¡£ÍýÏÀÅª¤Ë¤ÏR-Tree ¤Ï¤â¤Ã¤È¹â¤¤¼¡¸µ¤òÁàºî¤¹¤ë¤è¤¦¤Ë¤â³ÈÄ¥¤Ç¤¤Þ¤¹¡£¼Â¼ÁÅª¤Ë¤Ï¡¢R-Tree ¤Î³ÈÄ¥¤Ë¤Ï¤Á¤ç¤Ã¤È¤·¤¿ºî¶È¤¬É¬Í×¤Ç¤·¤Æ¡¢¸½ºß¡¢²æ¡¹¤Ï¤½¤ì¤ò¤É¤Î¤è¤¦¤Ë¤¹¤ë¤«¤Ë¤Ä¤¤¤Æ¤ÎÊ¸½ñ¤ò»ý¤Ã¤Æ¤¤¤Þ¤»¤ó¡£
+
 
-
-
+     [ÌõÃí¡§
 	R-Tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤ÏGiST¤Ç³«È¯¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
 	http://www.sai.msu.su/~megera/postgres/gist/
     ]
-
+
 
 
-
 
4.11)	°äÅÁÅªÌä¤¤¹ç¤ï¤»ºÇÅ¬²½¤È¤Ï²¿¤Ç¤¹¤«¡©
 
 
  GEQO ¥â¥¸¥å¡¼¥ë¤Ï¡¢Âô»³¤Î¥Æ¡¼¥Ö¥ë¤ò·ë¹ç¤¹¤ë¤È¤¤Ë¡¢°äÅÁÅª¥¢¥ë¥´¥ê¥º¥à(GA)¤ÇÌä¹ç¤ï¤»¤ò¹âÂ®²½¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢¤·¤é¤ß¤Ä¤Ö¤·¤ËÃµº÷¤ò¹Ô¤Ê¤ï¤Ê¤¯¤Æ¤â¡¢Âç¤¤Ê·ë¹ç(join queries)¤ò°·¤¦¤³¤È¤¬¤Ç¤¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
+
 
-
 
4.12)	Àµµ¬É½¸½¤Ç¤Î¸¡º÷¤äÂçÊ¸»ú¤È¾®Ê¸»ú¤È¤ò¶èÊÌ¤·¤Ê¤¤Àµµ¬É½¸½¸¡º÷¤Ï¤É¤Î¤è¤¦¤Ë¼Â¸½¤·¤Þ¤¹¤«¡©ÂçÊ¸»ú¤È¾®Ê¸»ú¤È¤ò¶èÊÌ¤·¤Ê¤¤¸¡º÷¤Î¤¿¤á¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¤É¤Î¤è¤¦¤Ë»È¤¤¤Þ¤¹¤«¡©
 
 
 
 ~±é»»»Ò¤ÏÀµµ¬É½¸½¾È¹ç¤ò¹Ô¤Ê¤¤¡¢~* ¤ÏÂçÊ¸»ú¤È¾®Ê¸»ú¤ò¶èÊÌ¤·¤Ê¤¤(case-insensitive)Àµµ¬É½¸½¾È¹ç¤ò¹Ô¤¤¤Þ¤¹¡£ ÂçÊ¸»ú¤È¾®Ê¸»ú¤ò¶èÊÌ¤·¤Ê¤¤ LIKE ±é»»»Ò¤ò ILIKE ¤È¤¤¤¤¤Þ¤¹¡£
-
+
 
 ÂçÊ¸»ú¤È¾®Ê¸»ú¤ò¶èÊÌ¤·¤Ê¤¤ÅùÃÍÈæ³Ó¤Ï¼¡¤Î¤è¤¦¤ËÉ½¸½¤Ç¤¤ë¡§
+
    
      SELECT *
     FROM tab
     WHERE lower(col) = 'abc';
 
-
+
 É¸½à¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤Ï»È¤ï¤ì¤º¡¢¤·¤«¤·¤Ê¤¬¤é¡¢¤â¤·´Ø¿ô¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò
 ºî¤Ã¤¿¤Ê¤é¤½¤ì¤¬»È¤ï¤ì¤ë¤Ç¤·¤ç¤¦¡£
-
+
        CREATE INDEX tabindex ON tab (lower(col));
    
 
 
-
 
4.13)	Ìä¤¤¹ç¤ï¤»¤ÎÃæ¤Ç¡¢¥Õ¥£¡¼¥ë¥É¤¬ NULL ¤Ç¤¢¤ë¤³¤È¤ò¸¡½Ð¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
 
 
     ¥«¥é¥à¤ò IS NULL ¤È IS NOT NULL
 ¤È¤Ç»î¤·¤Æ¤ß¤Þ¤¹¡£
 
-
 
4.14)	ÍÍ¡¹¤ÊÊ¸»ú·¿¤Î¤½¤ì¤¾¤ì¤Î°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©
 
 
@@ -1086,17 +1103,18 @@ BYTEA           bytea           
 
 
  ÆâÉôÌ¾¤Ë¤ªÌÜ¤Ë¤«¤«¤ë¤Î¤Ï¡¢¥·¥¹¥Æ¥à¡¦¥«¥¿¥í¥°¤òÄ´¤Ù¤ë¤È¤¤ä¡¢¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤ë¤È¤¤Ç¤¹¡£
-
+
 
  ¾åµ¤Î·¿¤Î¤¦¤ÁºÇ½é¤Î£´¤Ä¤Î·¿¤Ï "varlena" ·¿¤Ç¤¹(¤¹¤Ê¤ï¤Á¡¢¥Ç¥£¥¹¥¯¤ÎºÇ½é¤Î£´¥Ð¥¤¥È¤¬¥Ç¡¼¥¿Ä¹¤Ç¡¢¤½¤ì¤Î¸å¤Ë¼ÂºÝ¤Î¥Ç¡¼¥¿¤¬Â³¤¤Þ¤¹)¡£¤³¤Î¤è¤¦¤Ë¼ÂºÝ¤Î¶õ´Ö¤ÏÀë¸À¤µ¤ì¤¿Âç¤¤µ¤è¤ê¤â¾¯¤·Âç¤¤¯¤Ê¤ê¤Þ¤¹¡£¤·¤«¤·¡¢¤³¤ì¤é¤Î¥Ç¡¼¥¿·¿¤ÏTOAST¤Ë¤è¤ê°µ½Ì¤µ¤ì¤¿¤êÊ£¿ô¥í¥¦¤ËÅÏ¤Ã¤ÆÊÝÂ¸¤µ¤ì¤¿¤ê¤·¤Æ¡¢¥Ç¥£¥¹¥¯¾å¤Î¶õ´Ö¤Ï»×¤Ã¤¿¤è¤ê¾®¤µ¤¯¤Ê¤ê¤Þ¤¹¡£
+
 
 VARCHAR(n) ¤Ï²ÄÊÑÄ¹¤ÎÊ¸»úÎó¤òÊÝÂ¸¤¹¤ë¤Î¤ËºÇÅ¬¤Ç¤¹¤¬¡¢ÊÝÂ¸¤Ç¤¤ëÊ¸»úÎó¤ÎÄ¹¤µ¤ËÀ©¸Â¤¬¤¢¤ê¤Þ¤¹¡£TEXT ¤ÏÄ¹¤µ¤ËÀ©¸Â¤ÎÌµ¤¤Ê¸»úÎó¤ÎÊÝÂ¸¤Î¤¿¤á¤Î¤â¤Î¤Ç¡¢ºÇÂç¤Ç 1¥®¥¬¥Ð¥¤¥È¤Ç¤¹¡£ CHAR(n)¤Ï¡¢VARCHAR(n)¤¬Í¿¤¨¤é¤ì¤¿Ê¸»ú¤À¤±¤òÊÝÂ¸¤¹¤ë¤Î¤ËÂÐ¤·¡¢¥Ö¥é¥ó¥¯¤òµÍ¤á¹þ¤ó¤Ç¤¤¤Ä¤âÆ±¤¸Ä¹¤µ¤ÇÊ¸»úÎó¤òÊÝÂ¸¤¹¤ë¤Î¤ËºÇÅ¬¤Ç¤¹¡£BYTEA¤Ï¡¢ÉôÊ¬Åª¤ËNULL ¤Î¥Ð¥¤¥È¤ò´Þ¤à¥Ð¥¤¥Ê¥ê¥Ç¡¼¥¿¤òÊÝÂ¸¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£¤³¤ì¤é¤Î¥¿¥¤¥×¤ÏÆ±¤¸¤¯¤é¤¤¤ÎÀÇ½ÆÃÀ¤ò¤â¤Á¤Þ¤¹¡£
 
-
 
4.15.1)	ÄÌÈÖ(serial)¡¿¼«Æ°ÁýÊ¬¥Õ¥£¡¼¥ë¥É¤Ï¤É¤Î¤è¤¦¤Ë¤Ä¤¯¤ê¤Þ¤¹¤«¡©
 
 
  PostgreSQL ¤Ï SERIAL ¥Ç¡¼¥¿·¿¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£¥«¥é¥à¾å¤Ë¥·¡¼¥±¥ó¥¹¤ò¼«Æ°ºîÀ®¤·¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢
+
 
  	CREATE TABLE person ( 
@@ -1104,7 +1122,9 @@ BYTEA           bytea           
 		name TEXT 
 	);
 
+
 ¤Ï¼«Æ°Åª¤Ë¼¡¤Î¤è¤¦¤ËËÝÌõ¤µ¤ì¤Þ¤¹:
+
  	CREATE SEQUENCE person_id_seq;
 	CREATE TABLE person ( 
@@ -1117,38 +1137,43 @@ BYTEA           bytea           
 	¤Ï¡¢ 7.3 ¤«¤é¤Ï¼«Æ°Åª¤Ë¤Ï¹Ô¤Ê¤ï¤ì¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¡£
     ]
 
-
+
 ÄÌÈÖ¤Ë¤Ä¤¤¤Æ¤Î¤â¤Ã¤È¾Ü¤·¤¤¾ðÊó¤Ï¡¢¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç create_sequence ¤ò¤´Í÷²¼¤µ¤¤¡£
+
  ¤Þ¤¿¡¢³Æ¥í¥¦¤ÎOID¥Õ¥£¡¼¥ë¥É¤ò°ì°ÕÃÍ¤È¤·¤Æ»È¤¦¤³¤È¤â¤Ç¤¤Þ¤¹¡£¤·¤«¤·¤Ê¤¬¤é¡¢¤â¤·¤â¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò¥À¥ó¥×¤·¤Æ¥ê¥í¡¼¥É¤¹¤ëÉ¬Í×¤¬¤¢¤ë¾ì¹ç¤Ï¡¢OID¤ò²¹Â¸¤¹¤ë¤¿¤á¤Ëpg_dump ¤Ç -o¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤«¡¢¤Þ¤¿¤Ï¡¢COPY WITH OIDS¥ª¥×¥·¥ç¥ó¤ò»È¤¦É¬Í×¤¬¤¢¤ê¤Þ¤¹¡£
-
+
 
 4.15.2)	SERIAL¥Ç¡¼¥¿·¿¤ËÁÞÆþ¤µ¤ì¤ëÃÍ¤Ï¡¢¤É¤¦¤¹¤ì¤ÐÆÀ¤é¤ì¤Þ¤¹¤«¡©
 
     ¤Ò¤È¤Ä¤ÎÊýË¡¤Ï¡¢nextval() ´Ø¿ô¤ò»È¤Ã¤Æ¤½¤ÎÃÍ¤òÁÞÆþ¤¹¤ëÁ°(before)¤Ë SEQUENCE ¥ª¥Ö¥¸¥§¥¯¥È¤«¤é¼¡¤Î SERIAL ÃÍ¤ò¼è¤ê½Ð¤·¡¢¤½¤ì¤«¤é¼ÂºÝ¤ËÁÞÆþ¤ò¤¹¤ë¤³¤È¤Ç¤¹¡£4.15.1 ¤Î¥Æ¡¼¥Ö¥ë¤ÎÎã¤ò»È¤¦¤È¤¹¤ë¤È¡¢µ¿»÷¸À¸ì¤Ç¤Ï¤³¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
+
 
  	new_id = execute("SELECT nextval('person_id_seq')");
 	execute("INSERT INTO person (id, name) VALUES (new_id, 'Blaise Pascal')");
 
 
+
 ¤½¤¦¤·¤Æ¡¢new_id ¤ËÊÝÂ¸¤·¤¿¿·¤·¤¤ÃÍ¤òÂ¾¤ÎÌä¤¤¹ç¤ï¤»¤Ë(¤¿¤È¤¨¤Ð¡¢person ¥Æ¡¼¥Ö¥ë¤ËÂÐ¤¹¤ë³°Éô¥¡¼(foreign key)¤Î¤è¤¦¤Ë)»È¤¦¤È¤è¤¤¤Ç¤·¤ç¤¦¡£¼«Æ°Åª¤Ëºî¤é¤ì¤¿SEQUENCE¥ª¥Ö¥¸¥§¥¯¥È¤ÎÌ¾Á°¤Ï¡¢<table>_<serialcolumn>_seq ¤Î¤è¤¦¤Ë¤Ê¤ê¡¢¤³¤Î¤¦¤Á¡¢table ¤È serialcolumn ¤Ï¤½¤ì¤¾¤ì¥Æ¡¼¥Ö¥ë¤ÎÌ¾Á°¤ÈSERIAL¥«¥é¥à¤ÎÌ¾Á°¤Ç¤¹¡£
+
 
-
 ¤¢¤ë¤¤¤Ï¡¢Í¿¤¨¤é¤ì¤¿SERIALÃÍ¤ò¡¢¤½¤ì¤¬´ûÄêÃÍ¤È¤·¤ÆÁÞÆþ¤µ¤ì¤¿¸å¤Ç(after)¡¢ currval() ´Ø¿ô¤ò»È¤Ã¤Æ¼è¤ê½Ð¤¹¤³¤È¤â¤Ç¤¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢
+
 
  	execute("INSERT INTO person (name) VALUES ('Blaise Pascal')");
 	new_id = execute("SELECT currval('person_id_seq')");
 
 
+
 ºÇ¸å¤Ë¡¢INSERTÊ¸¤«¤éÊÖ¤ëOID¤ò»È¤Ã¤Æ¡¢´ûÄêÃÍ¤ò¤ß¤Ä¤±¤ë¤³¤È¤â¤Ç¤¤Þ¤¹¤¬¡¢¤·¤«¤·¡¢oid¤ÎÃÍ¤Ï40²¯¤ËÃ£¤¹¤ë¤È¤â¤È¤ËÌá¤Ã¤Æ¤·¤Þ¤¤¡¢ºÇ¤â°Ü¿¢À¤ÎÄã¤¤¤ä¤êÊý¤È¤Ê¤ë¤Ç¤·¤ç¤¦¡£Perl DBI ¤Î DBD::Pg ¥â¥¸¥å¡¼¥ë¤ò»È¤¨¤Ð¡¢$sth->execute() ¤Î¸å¤Ë $sth->{pg_oid_status} ¤ò·ÐÍ³¤·¤Æ¤½¤Î OID ÃÍ¤ò»È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ï¤Ç¤¤Þ¤¹¡£
+
 
- 
 
4.15.3)	currval() ¤ÏÂ¾¤Î¥æ¡¼¥¶¤È¤Î¶¥¹ç¾õÂÖ¤Ë´Ù¤ë¤³¤È¤Ï¤Ê¤¤¤Ç¤¹¤«¡©
 
 
     ¤½¤ì¤Ï¤¢¤ê¤Þ¤»¤ó¡£currval() ¤Ï¡¢¤¹¤Ù¤Æ¤Î¥æ¡¼¥¶¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢¤¢¤Ê¤¿¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¤ËÍ¿¤¨¤é¤ì¤¿¸½ºß¤ÎÃÍ¤òÊÖ¤·¤Þ¤¹¡£
-
+
 
 4.15.4) ¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬ÃæÃÇ¤·¤¿¤È¤¤Ë¤â¤¦¤¤¤Á¤É¥·¡¼¥±¥ó¥¹ÈÖ¹æ¤¬»È¤ï¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©¥·¡¼¥±¥ó¥¹¡¿SERIAL¥«¥é¥à¤Ë¶õ¤¤¬¤¢¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
 
@@ -1156,17 +1181,18 @@ BYTEA           bytea           
     Æ±»þÀ¤ò²þÁ±¤¹¤ë¤¿¤á¤Ë¡¢¼Â¹ÔÃæ¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤Ë¡¢É¬Í×¤Ç¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬½ªÎ»¤¹¤ë¤Þ¤Ç¥í¥Ã¥¯¤µ¤ì¤Ê¤¤¥·¡¼¥±¥ó¥¹ÃÍ¤òÍ¿¤¨¤Æ¤¤¤Þ¤¹¡£¤³¤Î¤¿¤á¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬ÃæÃÇ¤µ¤ì¤ë¤ÈÈÖ¹æ³ä¤êÅö¤Æ¤Ë¥®¥ã¥Ã¥×¤òÀ¸¤¸¤Þ¤¹¡£
 
 
- 
 
4.16)	OID ¤È¤Ï²¿¤Ç¤¹¤«¡© TID ¤È¤Ï²¿¤Ç¤¹¤«¡©
 
 
  OID ¤È¤Ï°ì°Õ¤Î¥í¥¦ID ¤ËÂÐ¤¹¤ë PostgreSQL ¤ÎÅú¤¨¤Ç¤¹¡£PostgreSQL ¤ÎÃæ¤Ç¤Ä¤¯¤é¤ì¤ë¤¹¤Ù¤Æ¤Î¥í¥¦¤Ï°ì°Õ¤Î OID ¤òÆÀ¤Þ¤¹¡£initdb ¤ÇÈ¯À¸¤µ¤ì¤ë OID ¤Ï¤¹¤Ù¤Æ 16384 (include/access/transam.h ¤«¤é)¤è¤ê¾®¤µ¤ÊÃÍ¤Ç¤¹¡£initdb ¸å¤Î¤¹¤Ù¤Æ¤Î OID (¥æ¡¼¥¶ºîÀ®)¤Ï¤½¤ì°Ê¾å¤ÎÃÍ¤Ë¤Ê¤ê¤Þ¤¹¡£
 ´ûÄê¤Ç¤Ï¡¢¤³¤ì¤é¤¹¤Ù¤Æ¤Î OID¤Ï°ì¤Ä¤Î¥Ç¡¼¥Ö¥ë¤ä¥Ç¡¼¥¿¥Ù¡¼¥¹Æâ¤ËÎ±¤Þ¤é¤º¡¢PostgreSQL ¥¤¥ó¥¹¥È¥ì¡¼¥·¥ç¥óÁ´ÂÎ¤ÎÃæ¤Ç°ì°Õ¤Ç¤¹¡£
+
 
  PostgreSQL ¤Ï¥Æ¡¼¥Ö¥ë´Ö¤Î¥í¥¦¤ò·ë¤Ó¤Ä¤±¤ë¤¿¤á¤Ë¡¢¤½¤Î¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ëÆâ¤Ë OID ¤ò»È¤¤¤Þ¤¹¡£¤³¤Î OID ¤ÏÆÃÄê¤Î¥æ¡¼¥¶¤Î¥í¥¦¤ò¼±ÊÌ¤¹¤ë¤¿¤á¤ä·ë¹ç¤ÎÃæ¤Ç»È¤ï¤ì¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£OID ¤ÎÃÍ¤òÊÝÂ¸¤¹¤ë¤¿¤á¤Ë¤Ï OID ·¿¤ò¥«¥é¥à¤Ë»È¤¦¤³¤È¤ò¾©¤á¤Þ¤¹¡£¤è¤êÂ®¤¯¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë OID ¥Õ¥£¡¼¥ë¥É¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤òºî¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
 
   OID ¤Ï¡¢Á´¤Æ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ç»È¤ï¤ì¤ëÃæ±ûÎÎ°è¤«¤é¡¢Á´¤Æ¤Î¿·¤·¤¤¥í¥¦¤Ë³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£OID ¤òÂ¾¤Î²¿¤«¤ËÊÑ¤¨¤¿¤¤¡¢¤¢¤ë¤¤¤Ï¸µ¤Î OID ¤â¥Æ¡¼¥Ö¥ë¤È°ì½ï¤Ë¥³¥Ô¡¼¤·¤¿¤¤¤Î¤Ê¤é¡¢¤Ç¤¤Ê¤¯¤Ï¤¢¤ê¤Þ¤»¤ó¡£
 
+
 
          CREATE TABLE new_table(mycol int);
@@ -1177,36 +1203,38 @@ BYTEA           bytea           
 
 
  OID ¤Ï¡¢4¥Ð¥¤¥È¤ÎÀ°¿ô¤È¤·¤ÆÊÝÂ¸¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢40²¯¤ò±Û¤¨¤ë¤È°î¤ì¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£Ã¯¤â¤³¤ì¤¬µ¯¤¤¿¤ÈÊó¹ð¤·¤Æ¤¯¤ë¿Í¤Ï¤¤¤Þ¤»¤ó¤Ç¤·¤¿¤¬¡¢¤½¤¦¤Ê¤ëÁ°¤Ë¤³¤ÎÀ©¸Â¤ò¼è¤ê½ü¤¯¤³¤È¤ò·×²è¤·¤Æ¤¤¤Þ¤¹¡£
+
 
  TID ¤ÏÆÃÄê¤ÎÊªÍý¥í¥¦¤ò¤½¤Î¥Ö¥í¥Ã¥¯¤È¥ª¥Õ¥»¥Ã¥ÈÃÍ¤Ç¼±ÊÌ¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£TID ¤Ï¥í¥¦¤¬½¤Àµ¤µ¤ì¤¿¤êºÆ¥í¡¼¥É¤µ¤ì¤ë¤ÈÊÑ¤ï¤ê¤Þ¤¹¡£¤½¤ì¤é¤Î TID ¤Ï¡¢ÊªÍý¥í¥¦¤ò»Ø¤¹¤¿¤á¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹µºÜ¤Ç»È¤ï¤ì¤Þ¤¹¡£
+
 
-
 
4.17)	PostgreSQL ¤Ç»È¤ï¤ì¤ë¤¤¤¯¤Ä¤«¤ÎÍÑ¸ì¤Î°ÕÌ£¤Ï²¿¤Ç¤¹¤«¡©
 
 
  ¤¤¤¯¤Ä¤«¤Î¥½¡¼¥¹¥³¡¼¥É¤ä¸Å¤¤Ê¸½ñ¤ÎÃæ¤Ë¤Ï¡¢¤½¤ì¤¾¤ÎÀìÌçÊ¬Ìî¤ÎÃæ¤Ç¤â¤Ã¤È°ìÈÌÅª¤Ë»È¤ï¤ì¤ëÀìÌçÍÑ¸ì¤¬»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
+
 
 
- ¥Æ¡¼¥Ö¥ë(table)¡¢´Ø·¸(relation)¡¢¥¯¥é¥¹(class)
-
 ¥í¥¦(row)¡¢¥ì¥³¡¼¥É(record)¡¢¥¿¥Ã¥×¥ë(tuple)
-
 ¥«¥é¥à(column)¡¢¥Õ¥£¡¼¥ë¥É(field)¡¢Â°À(attribute)
-
 ¼èÆÀ(retrieve)¡¢ÁªÂò(select)
-
 ÃÖ´¹(replace)¡¢¹¹¿·(update)
-
 ÄÉ²Ã(append)¡¢ÁÞÆþ(insert)
-
 OID, Ï¢ÈÖ(serial value)
-
 ¥Ý¡¼¥¿¥ë(portal), ¥«¡¼¥½¥ë(cursor)
-
 ÎÎ°èÊÑ¿ô(range variable)¡¢¥Æ¡¼¥Ö¥ëÌ¾(table name)¡¢¥Æ¡¼¥Ö¥ëÊÌÌ¾(table alias)
+
 ¥Æ¡¼¥Ö¥ë(table)¡¢´Ø·¸(relation)¡¢¥¯¥é¥¹(class)
+ ¥í¥¦(row)¡¢¥ì¥³¡¼¥É(record)¡¢¥¿¥Ã¥×¥ë(tuple)
+ ¥«¥é¥à(column)¡¢¥Õ¥£¡¼¥ë¥É(field)¡¢Â°À(attribute)
+ ¼èÆÀ(retrieve)¡¢ÁªÂò(select)
+ ÃÖ´¹(replace)¡¢¹¹¿·(update)
+ ÄÉ²Ã(append)¡¢ÁÞÆþ(insert)
+ OID, Ï¢ÈÖ(serial value)
+ ¥Ý¡¼¥¿¥ë(portal), ¥«¡¼¥½¥ë(cursor)
+ ÎÎ°èÊÑ¿ô(range variable)¡¢¥Æ¡¼¥Ö¥ëÌ¾(table name)¡¢¥Æ¡¼¥Ö¥ëÊÌÌ¾(table alias)
 
 °ìÈÌÅª¤Ê¥Ç¡¼¥¿¥Ù¡¼¥¹ÍÑ¸ì¤Î¥ê¥¹¥È¤Ï¡§http://hea-www.harvard.edu/MST/simul/software/docs/pkgs/pgsql/glossary/glossary.html
 ¤Ç¸«¤Ä¤±¤é¤ì¤Þ¤¹¡£
 
-
 
4.18) ¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸ "ERROR: Memory exhausted in AllocSetAlloc()"¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
 
 
 ¤ª¤½¤é¤¯¡¢¥·¥¹¥Æ¥à¤Î²¾ÁÛ¥á¥â¥ê¡¼¤òÁ´¤Æ»È¤¤²Ì¤¿¤·¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë²ÄÇ½À¤¬¤¢¤ë¤«¡¢¥«¡¼¥Í¥ë¤¬¤¢¤ë¥ê¥½¡¼¥¹¤Ë¤Ä¤¤¤Æ¤â¤ÄÀ©¸ÂÃÍ¤¬Äã¤¹¤®¤ë²ÄÇ½À¤¬¤¢¤ê¤Þ¤¹¡£
 postmaster ¤ò»ÏÆ°¤¹¤ëÁ°¤Ë¤³¤ì¤ò»î¤·¤Æ¤ß¤Æ²¼¤µ¤¤¡§
+
 
  	ulimit -d 262144
@@ -1215,34 +1243,34 @@ href="http://hea-www.harvard.edu/MST/simul/software/docs/pkgs/pgsql/glossary/glo
 
  
 ¥·¥§¥ë¤Ë¤è¤Ã¤Æ¡¢¤É¤Á¤é¤«¤Ò¤È¤Ä¤¬À®¸ù¤¹¤ë¤Ç¤·¤ç¤¦¤¬¡¢¤³¤ì¤Ï¥×¥í¥»¥¹¤Î¥Ç¡¼¥¿¥»¥°¥á¥ó¥ÈÀ©¸Â¤ò¤è¤ê¹â¤¯ÀßÄê¤·¡¢¤¿¤Ö¤óÌä¤¤¹ç¤ï¤»¤¬´°·ë¤¹¤ë¤è¤¦¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£¤³¤Î¥³¥Þ¥ó¥É¤Ï¸½¹Ô¤Î¥×¥í¥»¥¹¤È¡¢¤³¤Î¥³¥Þ¥ó¥É¤òÁö¤é¤»¤¿¸å¤Ëºî¤é¤ì¤ëÁ´¤Æ¤Î¥µ¥Ö¥×¥í¥»¥¹¤Ë¤Ä¤¤¤ÆÅ¬ÍÑ¤µ¤ì¤Þ¤¹¡£¥Ð¥Ã¥¯¥¨¥ó¥É¤¬¤È¤Æ¤âÂ¿¤¯¤Î¥Ç¡¼¥¿¤òÊÖ¤¹¤¿¤á¤ËSQL ¥¯¥é¥¤¥¢¥ó¥È¤ÇÌäÂê¤¬Â³¤¤¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢¥¯¥é¥¤¥¢¥ó¥È¤ò³«»Ï¤¹¤ëÁ°¤Ë¤³¤ì¤ò»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
+
 
-
 
4.19) ¤É¤Î¥Ð¡¼¥¸¥ç¥ó¤Î PostgreSQL ¤òÁö¤é¤»¤Æ¤¤¤ë¤«¤òÄ´¤Ù¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©

 
 
 psql ¤«¤é SELECT version(); ¤ò¥¿¥¤¥×¤·¤Þ¤¹¡£
-

-
+
 
 4.20)	¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥È¤ÎÁàºî¤Çinvalid large obj descriptor ¤ò¼õ¤±¼è¤ê¤Þ¤·¤¿¡£¤Ê¤¼¤Ç¤·¤ç¤¦¤«¡©
 
 
 ¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥ÈÁàºî¤ò¤¹¤ë¤È¤¤Ï¡¢Á°¸å¤ËBEGIN WORK¤ÈCOMMIT¤òÉÕ¤±¤ëÉ¬Í×¤¬¤¢¤ê¤Þ¤¹¡£¤¹¤Ê¤ï¤Á¡¢lo_open ... lo_close¤ò¤Ï¤µ¤ß¹þ¤ß¤Þ¤¹¡£
+
 
 ¸½ºß¤Ï¡¢PostgreSQL¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤Î¥³¥ß¥Ã¥È»þ¤Ë¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥È¡¦¥Ï¥ó¥É¥ë¤òÊÄ¤¸¤ë¤³¤È¤Ë¤è¤ê¡¢lo_open¥³¥Þ¥ó¥É¤¬´°Î»¤·¤¿Ä¾¸å¤Ë¶¯À©Åª¤Ë¥ë¡¼¥ë¤ò¼Â¹Ô¤·¤Þ¤¹¡£¤³¤Î¤¿¤á¡¢ºÇ½é¤Ë¥Ï¥ó¥É¥ë¤ËÂÐ¤·¤Æ²¿¤«¤ò¤·¤è¤¦¤È¤¹¤ë¤È¡¢invalid large obj descriptor(¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥È¤Îµ½Ò»Ò¤¬ÉÔÀµ)¤È¤Ê¤ê¤Þ¤¹¡£¤½¤ì¤Ç¡¢¤â¤·¡¢¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤ò»È¤¦¤Î¤òËº¤ì¤ë¤È¡¢¡Ê¾¯¤Ê¤¯¤È¤â¤Û¤È¤ó¤É¤Î»þ´Ö¡ËÆ¯¤¤¤Æ¤¤¤¿¥³¡¼¥É¤¬¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò½Ð¤¹¤Î¤Ç¤¹¡£
+
 
 ¤â¤·¡¢ODBC¤Î¤è¤¦¤Ê¥¯¥é¥¤¥¢¥ó¥È¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤ò¤ª»È¤¤¤Ê¤é¡¢auto-commit off¤òÀßÄê¤¹¤ëÉ¬Í×¤¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
-

+
 
 
 4.21) ¸½ºß¤Î»þ¹ï¤¬¥Ç¥Õ¥©¥ë¥È¤È¤Ê¤ë¤è¤¦¤Ê¥«¥é¥à¤Ï¤É¤Î¤è¤¦¤Ë¤Ä¤¯¤ê¤Þ¤¹¤«¡©

 
 CURRENT_TIMESTAMP¤ò»È¤¤¤Þ¤¹:
+
  	CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
 
-
-
 
 
4.22)	¤Ê¤¼¡¢IN¤ò»È¤¦ÉûÌä¤¤¹ç¤ï¤»¤¬¤È¤Æ¤âÃÙ¤¤¤Î¤Ç¤¹¤«¡©
 
@@ -1256,14 +1284,18 @@ href="http://hea-www.harvard.edu/MST/simul/software/docs/pkgs/pgsql/glossary/glo
 	FROM tab
 	WHERE col IN (SELECT subcol FROM subtab)
 
+
 ¤ò¡¢ÃÖ¤´¹¤¨¤Æ¡§
+
  	SELECT *
 	FROM tab
 	WHERE EXISTS (SELECT subcol FROM subtab WHERE subcol = col)
 
+
 ¤È¤·¤Þ¤¹¡£
 ¤³¤ì¤¬¼ê¤Ã¼è¤êÁá¤¤¤Ç¤¹¤¬¡¢subcol¤Ïº÷°úÉÕ¤¥«¥é¥à¤Ç¤¢¤ë¤Ù¤¤Ç¤¹¡£
+
 ¥Ð¡¼¥¸¥ç¥ó7.4°Ê¹ß¤Ç¤Ï¡¢IN¤Ï¡¢ÄÌ¾ï¤ÎÌä¤¤¹ç¤ï¤»¤ÈÆ±ÍÍ¤ÎÀöÎý¤µ¤ì¤¿¥¸¥ç¥¤¥ó¤Îµ»½Ñ¤ò¼ÂºÝ¤Ë»È¤¤¡¢EXISTS¤ò»È¤¦¤³¤È¤ò¹¥¤ß¤Þ¤¹¡£
 
 
@@ -1272,22 +1304,26 @@ href="http://hea-www.harvard.edu/MST/simul/software/docs/pkgs/pgsql/glossary/glo
 4.23) ³°Éô·ë¹ç(outer join)¤Ï¤É¤Î¤è¤¦¤Ë¼Â¸½¤·¤Þ¤¹¤«?

 
 PostgreSQL ¤Ï SQL É¸½à¹½Ê¸¤ò»È¤¦³°Éô·ë¹ç(¥¢¥¦¥¿¡¼¥¸¥ç¥¤¥ó)¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£¤³¤³¤Ë 2¤Ä¤ÎÎãÂê¤¬¤¢¤ê¤Þ¤¹¡£
+
 
  	SELECT *
 	FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
 
+
 ¤¢¤ë¤¤¤Ï
+
  	SELECT *
 	FROM t1 LEFT OUTER JOIN t2 USING (col);
 
-
+
 ¤³¤ì¤é¤Î¾ÝÄ§Åª¤ÊÌä¤¤¹ç¤ï¤»¤Ç¤Ï t1.col ¤ò t2.col ¤È·ë¹ç¤·¤Æ¡¢t1 ¤Î·ë¹ç¤µ¤ì¤Ê¤«¤Ã¤¿¥í¥¦(t2 ¤È°ìÃ×¤·¤Ê¤«¤Ã¤¿¥í¥¦)¤âÊÖ¤·¤Æ¤¤¤Þ¤¹¡£RIGHT ·ë¹ç¤Ï t2 ¤Î·ë¹ç¤µ¤ì¤Ê¤«¤Ã¤¿¥í¥¦¤ò²Ã¤¨¤ë¤Ç¤·¤ç¤¦¡£FULL ·ë¹ç¤Ï¡¢°ìÃ×¤·¤¿¥í¥¦¤Ë t1 ¤È t2 ¤«¤é¤Ï·ë¹ç¤µ¤ì¤Ê¤«¤Ã¤¿¥í¥¦¤òÊÖ¤¹¤Ç¤·¤ç¤¦¡£OUTER ¤È¤¤¤¦¸ÀÍÕ¤Ï¥ª¥×¥·¥ç¥ó¤Ç LEFT, RIGHT, ¤Þ¤¿¤Ï FULL ¤Ê¤É¤Î·ë¹ç¤ò²¾Äê¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ÄÌ¾ï¡¢·ë¹ç¤ÏINNER·ë¹ç¤È¸Æ¤Ð¤ì¤Þ¤¹¡£
-
+
+
 °ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï³°Éô·ë¹ç(outer join)¤òUNION ¤È NOT IN ¤ò»È¤Ã¤Æ¥·¥ß¥å¥ì¡¼¥È¤Ç¤¤Þ¤¹¡£
 ¤¿¤È¤¨¤Ð¡¢tab1 ¤È tab2 ¤ò·ë¹ç¤¹¤ë¤È¤¤Ï¡¢¼¡¤ÎÌä¤¤¹ç¤ï¤»¤ÇÆó¤Ä¤Î¥Æ¡¼¥Ö¥ë¤ò³°Éô·ë¹ç¤·¤Þ¤¹¡£
-
+
  	SELECT tab1.col1, tab2.col2
 	FROM tab1, tab2
@@ -1299,23 +1335,20 @@ PostgreSQL 
 	ORDER BY col1
 
 
-
 
4.24)  Ê£¿ô¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»È¤¦Ìä¤¤¹ç¤ï¤»¤Ï¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð¤Ç¤¤Þ¤¹¤«¡©

 
 
 ¸½¹Ô¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹°Ê³°¤Ø¤ÎÌä¤¤¹ç¤ï¤»ÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤È¤¤¤¦¤Î¤âPostgreSQL¤¬¥Ç¡¼¥¿¥Ù¡¼¥¹»ÅÍÍ¤Î¥·¥¹¥Æ¥à¥«¥¿¥í¥°¤òÆÉ¤ß¹þ¤à¤¿¤á¤Ç¡¢¤½¤³¤Ë¤Ï¡¢¤¿¤È¤¨¤½¤Î¤Õ¤ê¤ò¤¹¤ë¤À¤±¤Ë¤·¤í¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò±Û¤¨¤ÆÌä¤¤¹ç¤ï¤»¤ò¤¹¤ë¤¹¤Ù¤¬¤¢¤ê¤Þ¤»¤ó¡£
-

+

 contrib/dblink ¤Ï¥Ç¡¼¥¿¥Ù¡¼¥¹´Ö(cross-database)¤ÎÌä¤¤¹ç¤ï¤»¤ò´Ø¿ô¸Æ½Ð¤·¤Ë¤è¤êµö¤·¤Þ¤¹¡£¤â¤Á¤í¤ó¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÏÆ±»þ¤ËÀÜÂ³¤òÊÌ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ø¤âÄ¥¤é¤Ê¤¯¤Æ¤Ï¤Ê¤é¤º¡¢·ë²Ì¤ò¥¯¥é¥¤¥¢¥ó¥ÈÂ¦¤Ç¥Þ¡¼¥¸¤·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
 
 
-
 
4.25) ´Ø¿ô¤ÇÊ£¿ô¤Î¥í¥¦¤Þ¤¿¤Ï¥«¥é¥à¤òÊÖ¤¹¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©

 
 7.3¤Ç¤Ï´Ø¿ô¤«¤é¡¢Ê£¿ô¤Î¥í¥¦¤äÊ£¿ô¥«¥é¥à¤ò´ÊÃ±¤ËÊÖ¤»¤Þ¤¹¡£
 http://techdocs.postgresql.org/guides/SetReturningFunctions¡£
+
 
-
-
 
4.26)¤Ê¤¼¡¢PL/PgSQL ´Ø¿ô¤ÎÃæ¤«¤é°ì»þ¥Æ¡¼¥Ö¥ë¤ò³Î¼Â¤Ë create/drop ¤¹¤ë¤³¤È¤¬¤Ç¤¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¤«¡©
 
 PL/PgSQL ¤Ï´Ø¿ô¤ÎÆâÍÆ¤ò¥¥ã¥Ã¥·¥å¤·¡¢¤½¤ÎÉÔ¹¬¤ÊÉûºîÍÑ¤Î¤¿¤á¡¢¤â¤· PL/PgSQL ´Ø¿ô¤¬°ì»þ¥Æ¡¼¥Ö¥ë¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤È¡¢¤½¤Î¥Æ¡¼¥Ö¥ë¤Ï¤¢¤È¤Ç¥É¥í¥Ã¥×¤µ¤ìºÆºîÀ®¤µ¤ì¤Þ¤¹¤¬¡¢´Ø¿ô¤¬ºÆ¤Ó¸Æ¤Ó½Ð¤µ¤ì¤ë¤È¡¢¥¥ã¥Ã¥·¥å¤µ¤ì¤Æ¤¤¤ë¤½¤Î´Ø¿ô¤ÎÆâÍÆ¤Ï¤Þ¤À¸Å¤¤°ì»þ¥Æ¡¼¥Ö¥ë¤ò°ÍÁ³¤È¤·¤Æ»Ø¤·¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£²ò·èºö¤Ï¡¢ PL/PgSQL ¤ÎÃæ¤Ç EXECUTE ¤ò°ì»þ¥Æ¡¼¥Ö¥ë¥¢¥¯¥»¥¹¤Î¤¿¤á¤Ë»È¤¦¤³¤È¤Ç¤¹¡£¤³¤ì¤Ç¡¢Ëè²óÌä¤¤¹ç¤ï¤»¤ò¥Ñ¡¼¥¹¤·Ä¾¤¹¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
@@ -1336,7 +1369,6 @@ PL/PgSQL 
 
 
 
-
 
 [ÌõÃí
    ¥ì¥×¥ê¥±¡¼¥·¥ç¥ó´ØÏ¢¤Î¹àÌÜ¤¬¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¤¬¡¢ÌõÃí¤Î¤ß»Ä¤·¤Æ¤¢¤ê¤Þ¤¹¡£
@@ -1355,41 +1387,37 @@ PL/PgSQL 
 	http://www.postgresql.jp/wg/dt/index.html
 ]
 
-
 
 
-

 

 PostgreSQL¤Î³ÈÄ¥¤Ë¤Ä¤¤¤Æ¤Î¼ÁÌä
-
 
 
5.1)	¼«Ê¬¤Ç½ñ¤¤¤¿¥æ¡¼¥¶ÄêµÁ´Ø¿ô¤ò psql ¤ÎÃæ¤Ç¼Â¹Ô¤¹¤ë¤È¥³¥¢¡¦¥À¥ó¥×¤·¤Æ¤·¤Þ¤¦¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
 
 
  ÌäÂê¤Ï¿§¡¹¤È¹Í¤¨¤é¤ì¤Þ¤¹¤¬¡¢¤Þ¤ººÇ½é¤Ë¡¢ºîÀ®¤·¤¿¥æ¡¼¥¶ÄêµÁ´Ø¿ô¤òÃ±ÆÈ¤Î¥Æ¥¹¥È¥×¥í¥°¥é¥à¤Ë¤·¤Æ»î¤·¤Æ¤ß¤Æ²¼¤µ¤¤¡£
+
 
-
-
 
5.2)	PostgreSQL ÍÑ¤Ë½ñ¤¤¤¿¤Á¤ç¤Ã¤ÈÁÇÅ¨¤Ê¿·¤·¤¤·¿¤ä´Ø¿ô¤òÄó¶¡¤·¤Æ¥×¥í¥¸¥§¥¯¥È¤Ë¹×¸¥¤·¤¿¤¤¤Î¤Ç¤¹¤¬¡©
 
 
  ³§¤µ¤ó¤Î¹Ô¤Ê¤Ã¤¿³ÈÄ¥¤ò¡¢pgsql-hackers ¥á¡¼¥ê¥ó¥°¡¦¥ê¥¹¥È¤ËÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£¤½¤·¤Æ¡¢¤æ¤¯¤æ¤¯¤Ï¤½¤¦¤·¤¿³ÈÄ¥¤¬ contrib/ ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤ËÆþ¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
+
 
-
 
5.3)	¥¿¥×¥ë¤òÊÖ¤¹ C¸À¸ì¤Î´Ø¿ô¤Ï¤É¤Î¤è¤¦¤Ë½ñ¤¤Þ¤¹¤«¡©
 
 
 ¥Ð¡¼¥¸¥ç¥ó7.3°Ê¹ß¤ÎPostgreSQL¤Ç¤Ï¡¢¥Æ¡¼¥Ö¥ë¤òÊÖ¤¹´Ø¿ô¤ò C, PL/PgSQL¡¢¤½¤·¤Æ SQL ¤Ë¤Æ´°Á´¤Ë¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£¾Ü¤·¤¯¤Ï¥×¥í¥°¥é¥Þ¥¬¥¤¥É¤Î¾ðÊó¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£C¤ÇÄêµÁ¤µ¤ì¤¿É½¤òÊÖ¤¹´Ø¿ô¤ÎÎãÂê¤¬contrib/tablefunc¤ÎÃæ¤Ë¤¢¤ê¤Þ¤¹¡£
+
 
-
-
5.4)	¥½¡¼¥¹¡¦¥Õ¥¡¥¤¥ë¤òÊÑ¹¹¤·¤Þ¤·¤¿¡£ºÆ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤âÊÑ²½¤¬¸«¤é¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
+
5.4)	¥½¡¼¥¹¡¦¥Õ¥¡¥¤¥ë¤òÊÑ¹¹¤·¤Þ¤·¤¿¡£ºÆ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤âÊÑ²½¤¬¸«¤é¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
 
 
  ¤¤¤¯¤Ä¤«¤Î Makefile ¤¬¥¤¥ó¥¯¥ë¡¼¥É¡¦¥Õ¥¡¥¤¥ë¤ËÂÐ¤·¤ÆÅ¬ÀÚ¤Ê°ÍÂ¸´Ø·¸¤ò»ý¤Ã¤Æ¤¤¤Þ¤»¤ó¡£make clean ¤ò¤·¤Æ¤«¤é¤â¤¦°ìÅÙ make ¤ò¹Ô¤Ê¤ï¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£¤â¤·¡¢GCC ¤ò¤ª»È¤¤¤Ç¤¢¤ì¤Ð configure ¤Î --enable-depend ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢¥³¥ó¥Ñ¥¤¥é¤Ë°ÍÂ¸´Ø·¸¤ò¼«Æ°Åª¤ËÄ´¤Ù¤µ¤»¤ë¤³¤È¤â¤Ç¤¤Þ¤¹¡£
+
 
-
 

-+ [ÌõÃí¡§
   ÆüËÜ¸ìÈÇ¤ÎÀ½ºî¤Ë¤Ä¤¤¤Æ¤Ï°Ê²¼¤ÎÄÌ¤ê¤Ç¤¹¡£
 
@@ -1426,7 +1454,6 @@ PL/PgSQL 
 
   ¤Ê¤ª¡¢¤³¤ÎÏÂÌõ¤Ë´Ø¤¹¤ë¤´°Õ¸«¤Ï(juk at PostgreSQL.jp)¤Þ¤Ç¤ª´ó¤»²¼¤µ¤¤¡£
 ]
-
-
+
 
 
diff --git a/doc/src/FAQ/FAQ_polish.html b/doc/src/FAQ/FAQ_polish.html
index a92b90d3136..0966aee27a2 100644
--- a/doc/src/FAQ/FAQ_polish.html
+++ b/doc/src/FAQ/FAQ_polish.html
@@ -237,7 +237,7 @@
 
     Tekst powy¿ej, jest klasyczn± licencj± BSD.
     Nie posiada ona ¿adnych restrykcji co do u¿ywania kodu ¼ród³owego.
-	 Podoba nam siê i nie zamierzamy jej zmieniaæ.
+	 Podoba nam siê i nie zamierzamy jej zmieniaæ.
 
     1.3) Na jakich systemach Unixowych dzia³a
 	      PostreSQL?
@@ -266,7 +266,7 @@
     Serwer mo¿e byæ uruchamiany na Windows NT i Win2k u¿ywaj±c
 	 bibliotek Cygwin, Cygnus Unix/NT. W pliku pgsql/doc/FAQ_MSWIN
 	 znajduj±cym siê w ¼ród³ach lub pod adresem: http://www.PostgreSQL.org/docs/faqs/text/FAQ_MSWIN na naszych stronach.

+    "http://www.postgresql.org/docs/faqs/text/FAQ_MSWIN">http://www.PostgreSQL.org/docs/faqs/text/FAQ_MSWIN na naszych stronach.

 	 Obecnie prowadzone s± prace nad stworzeniem wersji dla MS Win
 	 NT/200/XP. Je¶li chcesz siê dowiedzieæ o obecnym statusie tych prac
 	 zobacz G³ówny serwer ftp z dostêpem "anonymous" dla PostgreSQL znajduje
 	 siê ftp://ftp.PostgreSQL.org/pub.
-	 je¶li szukasz mirrorów sprawd¼ nasz± g³ówn± stronê www.

+	 je¶li szukasz mirrorów sprawd¼ nasz± g³ówn± stronê www.
 
     1.6) Gdzie mo¿na szukaæ wsparcia technicznego?
 
@@ -334,7 +334,7 @@
 	 mo¿na znale¼æ na stronach WWW PostgreSQL pod adresem:
 
     
-      http://www.PostgreSQL.org
+      http://www.PostgreSQL.org
     
 
     W sieci EFNet istnieje kana³ IRC #PostgreSQL. Ja, do
@@ -599,7 +599,7 @@
 	
 	
 	Wiêcej informacji na ten temat znajduje siê pod adresem See
-	http://techdocs.postgresql.org/guides/GUITools.
+	http://techdocs.postgresql.org/guides/GUITools.
 	 
 	 2.4) Za pomoc± jakich jêzyków programowania
 	 mo¿na siê komunikowaæ z PostgreSQL?
@@ -882,14 +882,13 @@
 	 pierwszych rzêdów, byæ mo¿e bêdzie konieczno¶æ wykonania zapytania do
 	 momentu a¿ zostan± znalezione po¿±dane wyniki.
 	 
-	 Aby otrzymaæ losowy rz±d, u¿yj:
+	 Aby otrzymaæ losowy rz±d, u¿yj:
 	      SELECT col
     FROM tab
     ORDER BY random()
     LIMIT 1;
 	 
-	
 
     4.3) Jak mogê uzyskaæ listê wszystkich tabel
 	 czy  innych rzeczy pod psql?
@@ -926,7 +925,6 @@
    ALTER TABLE tab DROP COLUMN old_col;
    COMMIT;
 	
-	
 
     4.5) Jaki jest maksymalny rozmiar dla rzêdu,
 	      tabeli i bazy danych?
@@ -1034,7 +1032,7 @@
 	 przy wykonywaniu z³±czeñ (join). Sekwencyjne przeszukiwanie po którym
 	 nastêpuje sortowanie jest zazwyczaj szybsze niê wyszukiwanie za
 	 pomoc± indeksu na du¿ej tabeli.
-	 Jakkolwiek LIMIT w po³±czeniu z ORDER BY
+	 Jakkolwiek LIMIT w po³±czeniu z ORDER BY
 	czêsto bêdzie wykorzystywa³ indeksy poniewa¿ jedynie ma³a czê¶æ z
 	tabeli jest zwracana. W rzeczywisto¶ci, chocia¿ MAX() i MIN() nie
 	u¿ywaj± indeksów, mo¿liwe jest aby zwróciæ te warto¶ci u¿ywaj±c
@@ -1049,7 +1047,7 @@
 	

 	Je¶li uwa¿asz, ¿e optimizer myli siê wybieraj±c sequential scan, u¿yj
 	SET enable_seqscan TO 'off' i uruchom testy aby sprawdziæ czy wtym
-	wypadku zapytanie bêdzie szybciej wykonywane.
+	wypadku zapytanie bêdzie szybciej wykonywane.
 
     Kiedy u¿ywa siê operatorów dopasuj±cych takich jak
 	 LIKE lub ~, indeksy bêd± u¿ywane jedynie w
@@ -1057,16 +1055,16 @@
 	 

 	 Pocz±tek wyszukiwania jest oparty na pocz±tku ³añcucha tekstu.
 	 
-	 	wzorce LIKE nie mog± siê zaczynaæ %
+	 	
wzorce LIKE nie mog± siê zaczynaæ %
 		dopasowania operatorem ~ (dopasowania regularne)
-		musz± siê zaczynaæ znakiem specjalnym ^.
-	 
+		musz± siê zaczynaæ znakiem specjalnym ^.
+	 
 	 Pocz±tek wyszukiwania nie mo¿e siê zaczynaæ od klas znaków, np.
-	 [a-e].
+	 [a-e].
 	 Case-insensitive searches such as ILIKE and ~* do not utilise
 	 indexes. Instead, use functional indexes, which are described in
-	 section 4.12.
-	 
Standardowe locale C musi byæ uzyte przy wykonywaniu initdb
+	 section 4.12.
+	 Standardowe locale C musi byæ uzyte przy wykonywaniu initdb
 	 
     4.9) Jak mogê sprawdziæ w jakis sposób "query
 	 optimizer" wykonuje moje zapytanie?
@@ -1165,7 +1163,7 @@ BYTEA           bytea              zmiennej d
 	 przechowywane out-of-line jako TOAST, wiêc faktyczne
 	 zu¿ycie miejsca na dysku mo¿e byæ mniejsze ni¿ oczekiwane.
 
-	 VARCHAR(n) jest
+	 VARCHAR(n) jest
 	 najodpowiedniejszy do przechowywania ³añcuchów o ró¿nej d³ugo¶ci
 	 ale okre¶la on maksymaln± jego d³ugo¶æ. 
 	 
@@ -1344,7 +1342,7 @@ BYTEA           bytea              zmiennej d
 
     
Listê terminów zwi±zanych z bazami danych mo¿esz znale¼æ pod tym
 	 adresem:http://hea-www.harvard.edu/MST/simul/software/docs/pkgs/pgsql/glossary/glossary.html.
+	 href="http://hea-www.harvard.edu/MST/simul/software/docs/pkgs/pgsql/glossary/glossary.html">http://hea-www.harvard.edu/MST/simul/software/docs/pkgs/pgsql/glossary/glossary.html.
 
     4.18) Sk±d bierze siê ten b³±d "ERROR:
 	 Memory exhausted in AllocSetAlloc()"?
@@ -1488,7 +1486,7 @@ BYTEA           bytea              zmiennej d
 	      kolumn?
 
      Mo¿esz w ³atwy sposób zwracaæ wiele rzêdów lub kolumn u¿ywaj±c
-	  funkcji z: http://techdocs.postgresql.org/guides/SetReturningFunctions.
+	  funkcji z: http://techdocs.postgresql.org/guides/SetReturningFunctions.
      
 	4.26) Dlaczego nie mogê w sposób pewny
 	     tworzyæ/usuwaæ tabel tymczasowych w funkcjach PL/PgSQL?
@@ -1503,38 +1501,36 @@ BYTEA           bytea              zmiennej d
 	funkcji.
 	
 	
-	4.27) Jakie s± mo¿liwo¶ci replikacji w PostgreSQL?

+	4.27) Jakie s± mo¿liwo¶ci replikacji w PostgreSQL?
 	
 	Jest kilka opcji aby stosowaæ replikacjê typu master/slave. Ten typ
 	pozwala jedynie masterowi na dokonywanie zmian w bazie danych, a
 	slave mo¿e jedynie te zmiany odczytywaæ. Na stronie 
 	http://gborg.PostgreSQL.org/genpage?replication_research
+	href="http://gborg.PostgreSQL.org/genpage?replication_research">http://gborg.PostgreSQL.org/genpage?replication_research
 	znajduje siê ich lista. Replikacja typu multi-master jest w trakcie
 	prac, opis projektu znajduje siê pod adresem: 
+	href="http://gborg.PostgreSQL.org/project/pgreplication/projdisplay.php">
 http://gborg.PostgreSQL.org/project/pgreplication/projdisplay.php.
 	
 
-	4.28) Jakie mo¿liwo¶ci szyfrowania oferuje
+	4.28) Jakie mo¿liwo¶ci szyfrowania oferuje
 	PostgreSQL?
-	
 	

 	contrib/pgcrypto zawiera wiele funkcji za pomoc±, których mo¿emy u¿ywaæ
-	kryptografii w zapytaniach SQL.
+	kryptografii w zapytaniach SQL.
 	Aby szyfrowaæ transmisjê od klienta do serwera, ten musi mieæ
 	ustawion± opcjê ssl na true w pliku postgresql.conf, odpowiedni
 	wpis host lub hostssl musi wystêpowaæ w pliku pg_hba.conf, oraz
 	sslmode nie mo¿e byæ wy³±czone w kliencie. (Warto zwróciæ uwagê, ¿e
 	mo¿liwe jest tak¿e u¿ywanie transportów szyfruj±ców przez strony
 	trzecie, takie jak stunnel lub ssh, poza natywnym wsparciem dla SSL
-	przez PostgreSQL).
+	przez PostgreSQL).
 	Has³a u¿ytkowników bazy danych s± automatycznie szyfrowane od
 	wersji 7.3. W poprzednich wersjach, nale¿y t± funkcjonalno¶æ poprzez
-	w³±czenie opcji PASSWORD_ENCRYPTION w postgresql.conf. 
-	
Serwer mo¿e dzia³aæ u¿ywaj±c szyfrowanego systemu plików.
+	w³±czenie opcji PASSWORD_ENCRYPTION w postgresql.conf. 
+	Serwer mo¿e dzia³aæ u¿ywaj±c szyfrowanego systemu plików.
 	
-
 
     
Rozwijanie PostgreSQL
 
diff --git a/doc/src/FAQ/FAQ_russian.html b/doc/src/FAQ/FAQ_russian.html
index debcc882666..bd515c7c79f 100644
--- a/doc/src/FAQ/FAQ_russian.html
+++ b/doc/src/FAQ/FAQ_russian.html
@@ -236,16 +236,16 @@
     http://techdocs.postgresql.org/companies.php.
 
 
-    1.6) ëÁË ÍÎÅ ÓÏÏÂÝÉÔØ ÏÂ ÏÛÉÂËÅ?
+    1.6) ëÁË ÍÎÅ ÓÏÏÂÝÉÔØ ÏÂ ÏÛÉÂËÅ?
     
     ðÏÓÅÔÉÔÅ ÓÔÒÁÎÉÞËÕ ÓÏ ÓÐÅÃÉÁÌØÎÏÊ ÆÏÒÍÏÊ ÏÔÞ£ÔÁ ÏÂ ÏÛÉÂËÅ ×
     PostgreSQL ÐÏ ÁÄÒÅÓÕ:
-    
+    
     http://www.postgresql.org/support/submitbug.
     
     ôÁËÖÅ ÐÒÏ×ÅÒØÔÅ ÎÁÌÉÞÉÅ ÂÏÌÅÅ Ó×ÅÖÅÊ ×ÅÒÓÉÉ PostgreSQL ÎÁ ÎÁÛÅÍ
     FTP ÓÁÊÔÅ 
-    ftp://ftp.PostgreSQL.org/pub.
+    ftp://ftp.PostgreSQL.org/pub.
     
 
     1.7) ëÁËÁÑ ÐÏÓÌÅÄÎÑÑ ×ÅÒÓÉÑ?
@@ -604,19 +604,18 @@
      ÄÌÑ ÎÅÓËÏÌØËÉÈ ÐÅÒ×ÙÈ ÓÔÒÏÞÅË ÚÁÐÒÏÓÁ? ðÒÏÉÚ×ÏÌØÎÏÊ ÓÔÒÏËÉ?
 
     äÌÑ ÐÏÌÕÞÅÎÉÑ ÔÏÌØËÏ ÎÅÓËÏÌØËÉÈ ÓÔÒÏË, ÅÓÌÉ ×Ù ÚÎÁÅÔÅ ÉÈ ËÏÌÉÞÅÓÔ×Ï
-    ÎÁ ÍÏÍÅÎÔ ×ÙÐÏÌÎÅÎÉÑ SELECT ÉÓÐÏÌØÚÕÊÔÅ LIMIT.
+    ÎÁ ÍÏÍÅÎÔ ×ÙÐÏÌÎÅÎÉÑ SELECT ÉÓÐÏÌØÚÕÊÔÅ LIMIT.
     åÓÌÉ ÅÓÔØ ËÁËÏÊ-ÌÉÂÏ ÉÎÄÅËÓ, ËÏÔÏÒÙÊ ÓÏ×ÐÁÄÁÅÔ Ó ORDER BY,
     ÔÏ ×ÏÚÍÏÖÎÏ, ÞÔÏ ×ÅÓØ ÚÁÐÒÏÓ ×ÙÐÏÌÎÅÎ É ÎÅ ÂÕÄÅÔ. åÓÌÉ ×Ù ÎÅ ÚÎÁÅÔÅ
     ËÏÌÉÞÅÓÔ×Á ÎÅÏÂÈÏÄÉÍÙÈ ÓÔÒÏË ÎÁ ÍÏÍÅÎÔ ×ÙÐÏÌÎÅÎÉÑ SELECT,
     ÉÓÐÏÌØÚÕÊÔÅ ËÕÒÓÏÒ É FETCH.
 
-    To SELECT a random row, use:
-
    SELECT col
+    To SELECT a random row, use:
+    SELECT col
     FROM tab
     ORDER BY random()
     LIMIT 1;
 
-
 
     4.2) ëÁË ÍÎÅ ÎÁÊÔÉ ËÁËÉÅ ÔÁÂÌÉÃÙ, ÉÎÄÅËÓÙ,
     ÂÁÚÙ ÄÁÎÎÙÈ É ÐÏÌØÚÏ×ÁÔÅÌÉ ÓÕÝÅÓÔ×ÕÀÔ? ëÁË ÍÎÅ Õ×ÉÄÅÔØ ÚÁÐÒÏÓÙ,
@@ -646,7 +645,7 @@
     
4.3) ëÁË ÉÚÍÅÎÉÔØ ÔÉÐ ÄÁÎÎÙÈ ËÏÌÏÎËÉ?
 
     ÷ 8.0 É ÂÏÌÅÅ ÐÏÚÄÎÉÈ ×ÅÒÓÉÑÈ, ÉÚÍÅÎÅÎÉÅ ÔÉÐÁ ËÏÌÏÎËÉ ×ÙÐÏÌÎÑÅÔÓÑ
-    ÏÞÅÎØ ÌÅÇËÏ ÞÅÒÅÚ ALTER TABLE ALTER COLUMN TYPE.
+    ÏÞÅÎØ ÌÅÇËÏ ÞÅÒÅÚ ALTER TABLE ALTER COLUMN TYPE.
 
     ÷ ÂÏÌÅÅ ÒÁÎÎÉÈ ×ÅÒÓÉÑÈ ÓÄÅÌÁÊÔÅ ÔÁË:
 @@ -662,7 +661,7 @@
 
     óÕÝÅÓÔ×ÕÀÔ ÓÌÅÄÕÀÝÉÅ ÏÇÒÁÎÉÞÅÎÉÑ:
 
-

 Type Internal Name Notes
 VARCHAR(n) varchar size specifies maximum
 length, no padding
 
     
 
     
     
 
     
     
      
     
      
     
 
     
 
     
 
     
 
       
     
     
       
       
    
 
 
+
@@ -775,7 +774,7 @@
     É × ÜÔÏÍ ÓÌÕÞÁÅ ÉÎÄÅËÓ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ, ÐÏÓËÏÌØËÕ ÐÒÉ ×ÙÐÏÌÎÅÎÉÉ
     ÂÕÄÅÔ ×ÏÚ×ÒÁÝÁÔØÓÑ ÎÅÂÏÌØÛÁÑ ÞÁÓÔØ ÔÁÂÌÉÃÙ. æÁËÔÉÞÅÓËÉ MAX() É MIN() ÎÅ
     ÉÓÐÏÌØÚÕÀÔ ÉÎÄÅËÓÙ, ÎÏ ÉÎÄÅËÓ ÉÓÐÏÌØÚÕÅÔÓÑ ÐÒÉ ÐÏÓÔÒÏÅÎÉÉ ÚÁÐÒÏÓÏ× Ó
-    ORDER BY É LIMIT:
+    ORDER BY É LIMIT:
     SELECT col
     FROM tab
@@ -833,8 +832,8 @@
     WHERE lower(col) = 'abc';
 
 
-    üÔÁ ËÏÎÓÔÒÕËÃÉÑ ÎÅ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÓÔÁÎÄÁÒÔÎÙÊ ÉÎÄÅËÓ. ïÄÎÁËÏ, ÅÓÌÉ
-    ×Ù ÓÏÚÄÁÄÉÔÅ ÉÎÄÅËÓ ×ÙÒÁÖÅÎÉÑ, ÏÎ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎ:
+    üÔÁ ËÏÎÓÔÒÕËÃÉÑ ÎÅ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÓÔÁÎÄÁÒÔÎÙÊ ÉÎÄÅËÓ. ïÄÎÁËÏ, ÅÓÌÉ
+    ×Ù ÓÏÚÄÁÄÉÔÅ ÉÎÄÅËÓ ×ÙÒÁÖÅÎÉÑ, ÏÎ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎ:
     CREATE INDEX tabindex ON tab (lower(col));
 
@@ -848,7 +847,7 @@
     4.10) ëÁËÏ×Ù ÏÔÌÉÞÉÑ ÍÅÖÄÕ ÒÁÚÎÙÍÉ ÓÉÍ×ÏÌØÎÙÍÉ
      ÔÉÐÁÍÉ?

-

 
 
   íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÂÁÚÙ?
 
 
 
+
@@ -919,7 +918,7 @@
     );
 
 
-    Á×ÔÏÍÁÔÉÞÅÓËÉ ÔÒÁÎÓÌÉÒÕÅÔÓÑ ×: 
+    Á×ÔÏÍÁÔÉÞÅÓËÉ ÔÒÁÎÓÌÉÒÕÅÔÓÑ ×: 
     CREATE SEQUENCE person_id_seq;
     CREATE TABLE person ( 
@@ -994,12 +993,12 @@
     OID, ÐÏÔÏÍÕ ÞÔÏ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ SERIAL
     ÕÎÉËÁÌØÎÙ ÔÏÌØËÏ ×ÎÕÔÒÉ ÔÁÂÌÉÃÙ É ÔÁËÉÍ ÏÂÒÁÚÏÍ ÍÅÎØÛÅ ÐÏÄ×ÅÒÖÅÎÙ
     ÐÅÒÅÐÏÌÎÅÎÉÀ. äÌÑ ÈÒÁÎÅÎÉÑ ÚÎÁÞÅÎÉÊ 8-ÍÉ ÂÁÊÔÎÏÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ
-    ÄÏÓÔÕÐÅÎ ÔÉÐ SERIAL8.
+    ÄÏÓÔÕÐÅÎ ÔÉÐ SERIAL8.
 
     TID ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÉÄÅÎÔÉÆÉËÁÃÉÉ ÓÐÅÃÉÁÌØÎÙÈ
     ÆÉÚÉÞÅÓËÉÈ ÚÁÐÉÓÅÊ Ó ÂÌÏÞÎÙÍÉ É offset ÚÎÁÞÅÎÉÑÍÉ. TID
     ÉÚÍÅÎÑÅÔÓÑ ÐÏÓÌÅ ÔÏÇÏ ËÁË ÓÔÒÏËÉ × ÔÁÂÌÉÃÅ ÂÙÌÉ ÉÚÍÅÎÅÎÙ ÉÌÉ ÐÅÒÅÇÒÕÖÅÎÙ.
-    
TID ÉÓÐÏÌØÚÕÅÔÓÑ ÉÎÄÅËÓÎÙÍÉ ÚÁÐÉÓÑÍÉ × ËÁÞÅÓÔ×Å
+    TID ÉÓÐÏÌØÚÕÅÔÓÑ ÉÎÄÅËÓÎÙÍÉ ÚÁÐÉÓÑÍÉ × ËÁÞÅÓÔ×Å
     ÕËÁÚÁÔÅÌÑ ÎÁ ÆÉÚÉÞÅÓËÉÅ ÚÁÐÉÓÉ.
 
 
diff --git a/doc/src/FAQ/FAQ_turkish.html b/doc/src/FAQ/FAQ_turkish.html
index e0921f64970..ac31a57ab76 100644
--- a/doc/src/FAQ/FAQ_turkish.html
+++ b/doc/src/FAQ/FAQ_turkish.html
@@ -111,7 +111,7 @@ adreslerinde g
 	4.18) Neden "ERROR: Memory exhausted in AllocSetAlloc()"
 	hatasýný alýyorum?

 	4.19) Hangi PostgreSQL sürümünü çalýstýrdýðýmý nasýl görebilirim?

-	4.20) Neden large-object iþlemlerim, "invalid large
+	4.20) Neden large-object iþlemlerim, "invalid large
 	obj descriptor" hatasýný veriyor?

 	4.21) Þu andaki zamaný öntanýmlý deðer olarak kabul
 	eden kolonu nasýl yaratýrým?

@@ -190,7 +190,7 @@ adreslerinde g
 	        PostgreSQL 8.0 sürümü ile , PostgreSQL artýk Win2000, WinXP ve Win2003 gibi Microsoft 
 		Windows NT tabanlý iþletim sistemlerinde doðal olarak çalýþmaya baþlamýþtýr. Paketlenmiþ bir
 		kurulum programý, http://pgfoundry.org/projects/pginstaller. adresinden 
-		indirilebilir.
+		indirilebilir.
 
 		Ayrýca, http://forge.novell.com adresinde Novell Netware 6 portu bulunmaktadýr.
 		
@@ -218,7 +218,7 @@ adreslerinde g
 		subscribe
end
 		yazan bir e-posta atmanýz yeterli olacaktýr.
 		Bunun dýþýndaki e-posta listelerine ve PostgreSQL hakkýnda bilgiye, PostgreSQL WWW 
-		ana sayfasýndan ulasabilirsiniz: http://www.PostgreSQL.org

+		ana sayfasýndan ulasabilirsiniz: http://www.PostgreSQL.org
 		Ayný zamanda, EFNet üzerinde, #PostgreSQL adlý bir IRC kanalý
 		bulunmaktadýr. Bunun için, irc -c '#PostgreSQL' "$USER" irc.phoenix.net
 		Unix komutunu kullanabilirsiniz.
@@ -235,7 +235,7 @@ adreslerinde g
 		/doc dizinine bakýnýz. Ayrýca, bu el kitapçýklarýný online olarak
 		http://www.PostgreSQL.org/docs/ adresinden inceleyebilirsiniz.
 		http://www.PostgreSQL.org/docs/awbook.html
-		ve http://www.commandprompt.com/ppbook
+		ve http://www.commandprompt.com/ppbook
 		adreslerinde PostgreSQL kitaplarý bulunmaktadýr. PostgreSQL kitablarýnýn listesine, 
 		http://www.ca.PostgreSQL.org/books/ adresinden ulaþaiblirsiniz.
 		Ayrýca, PostgreSQL konusundaki teknik makalelere de
@@ -288,7 +288,7 @@ adreslerinde g
 		
1.14) PostgreSQL, diger DBMS'lerle nasýl karþýlastýrýlabilir?
 		Bir yazýlýmýn gücünü ölçmek için çeþitli yollar vardýr: Yazýlýmýn özellikleri, 
 		baþarýmý, güvenilirliði, desteði ve ücreti.
-		Özellikler:

+		
Özellikler:
 		PostgreSQL mevcut büyük ticari veritabanlarýnýn, transaction,
 		subselect, trigger, view, foreign key referential integrity
 		ve sophisticated locking gibi (user-defined types), rules,
@@ -355,7 +355,7 @@ adreslerinde g
 		
http://www.webreview.com/ adresinde,
 		arka planda veritabaný çalýstýran Web sayfalarý için giriþ seviyesinde bilgi bulunmaktadýr.
 		Web ile bütünleþme için, PHP ()
-		mükemmel bir arabirim sunar.

+		mükemmel bir arabirim sunar.
 		Karmaþýk sorunlar için, çoðu kisi Perl arabirimini ve CGI.pm ya da mod_perl kullanýr.
 		
 		2.3) PostgreSQL'in grafik kullanýcý arabirimi var mýdýr?
@@ -466,7 +466,7 @@ adreslerinde g
 		Postmaster ve postgres çeþitli hata ayýklama seçeneklerine sahiptir. Öncelikle,
 		postmaster'ý baþlattýðýnýzda, standart çýktýyý ve hatalarý bir log dosyasýna 
 		yönlendirdiðinize emin olun:
-		cd /usr/local/pgsql
./bin/postmaster >server.log 2>&1 &
+		cd /usr/local/pgsql
./bin/postmaster >server.log 2>&1 &
 		Bu iþlem PostgreSQL ana dizinine server.log dosyasý yerleþtirecektir.
 		Bu dosya sunucunun yaþadýðý sorunlar ya da hatalar hakkýnda yararlý bilgiler içerir.
 		-d seçeneði, hata ayýklama seviyesini belirten bir rakam ile kullanýlýr.
@@ -497,7 +497,7 @@ adreslerinde g
 		deðeri ile ya da postgresql.conf dosyasýný düzenleyerek yeniden
 		baþlatmakla arttýrabilirsiniz.
 		Eðer -N deðerini 32'den büyük yapacaksanýz, ayný zamanda
-		-B deðerini de deðiþtirmeniz gerektiðini unutmayýn. -B,
+		-B deðerini de deðiþtirmeniz gerektiðini unutmayýn. -B,
 		-N'nin en az 2 katý kadar olmalýdýr; daha iyi baþarým için bu sayýyý daha
 		da arttýrmalýsýnýz. Yüksek sayýdaki backend süreçleri için, çeþitli çekirdek
 		yapýlandýrma parametrelerini arttýrmanýz gerekecektir. Yapýlmasý gerekenler,
@@ -554,7 +554,7 @@ adreslerinde g
 		LIMIT ... kullanýnýz.
 		Ýlk birkaç satýrý almak isteseniz bile, tüm sorgu deðerlendirilmek durumunda kalýnabilir. ORDER 
  		BY içeren bir sorgu düþünün. Eðer ORDER BY iþe eþleþen bir index varsa, PostgreSQL istenen ilk birkaç  
-		satýrý iþleyebilir, ya da tüm sorgu istenen satýrlar üretilene kadar iþlenebilir. 
+		satýrý iþleyebilir, ya da tüm sorgu istenen satýrlar üretilene kadar iþlenebilir. 
 		
 		4.3) psql'in içinde gördügüm tablolarýn ya da diðer
 		þeylerin listesini nasýl alabilirim?
@@ -786,7 +786,7 @@ CREATE UNIQUE INDEX person_id_key ON person ( id );
     execute("INSERT INTO person (id, name) VALUES (new_id, 'Blaise Pascal')");
Diðer sorgular için new_id'de yeni deðerin saklanmasý gerekir. Otomatik olarak yaratýlan SEQUENE nesnesinin adý,
-  __seq þeklinde olacaktýr (< > iþaretleri olmadan).
+  <tablo adý>_<serial kolonu adý>_seq þeklinde olacaktýr (< > iþaretleri olmadan).
Alternatif olarak, atanmýþ SERIAL deðerini, deðer girildikten sonra currval()
 		fonksiyonu ile alabilirsiniz:
-- 
cgit v1.2.3


 
 
   ôÉÐ
Maximum size for a database?	unlimited (32 TB databases exist)
Maximum size for a table?	32 TB
unlimited
unlimited
Frequently Asked Questions (FAQ) for PostgreSQL

4.3) How do you change a column's data type?

4.10) What is the difference between the various character types?

4.20) Why do I get "missing oid" errors when - accessing temporary tables in PL/PgSQL functions?

4.20) Why do I get "relation with OID ##### + does not exist" errors when accessing temporary tables in PL/PgSQL + functions?

Developer's Frequently Asked Questions (FAQ) for PostgreSQL

General Questions

Technical Questions

General Questions

1.1) How go I get involved in PostgreSQL +

1.1) How do I get involved in PostgreSQL development?

1.5) Where can I learn more about the code?

1.18) How go I get involved in PostgreSQL +

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

Technical Questions

2.1) How do I efficiently access information in tables from the backend code?

Resources

1.5) Onde eu posso conseguir o PostgreSQL?

3.11) Que tipo de hardware eu devo usar?

4.23) Como eu faço uma junção externa (outer join)?

4.25) Como eu retorno múltiplos registros ou colunas de uma função?

4.26) Por que eu não posso confiar na criação/remoção de tabelas temporárias em funções PL/PgSQL?

4.27) Que opções para encriptação estão disponíveis?

Obecné otázky

1.1) Co je PostgreSQL? Jak se vyslovuje?

1.1) Co je PostgreSQL? Jak se vyslovuje?

1.7) Jaká je poslední verze?

4.15.3) Nepovede currval() a nextval() k rozhození podmínek pøi soubìhu s jinými u¾ivateli?

4.26) Proè nelze spolehlivì vytváøet a ru¹it doèasné tabulky v PL/pgSQL funkcích?

4.26) Pourquoi ne puis-je pas créer/supprimer des tables temporaires dans les fonctions PL/PgSQL de façon stable ?

1.5) Woher bekomme ich PostgreSQL?

1.6) Wo bekomme ich Support fÃ¼r PostgreSQL?

1.13) Wie sende ich einen Fehlerbericht?

2.4) Welche Programmiersprachen und Schnittstellen gibt es?

Administrative Fragen

Administrative Fragen

3.1) Wie installiere ich PostgreSQL woanders als in /usr/local/pgsql?

4.2) Wie wÃ¤hle ich per SELECT-Anweisung nur die ersten paar Zeilen bzw. eine beliebige Zeile in einer Abfrage aus?

4.16) Welche Bedeutung haben die verschiedenen AusdrÃ¼cke, die in PostgreSQL benutzt werden (z.B. attribute, class,...)?

PostgreSQL(¥Ý¥¹¥È¥°¥ì¥¹¡¦¥­¥å¡¼¡¦¥¨¥ë)¤Ë¤Ä¤¤¤Æ¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤Î²òÅú(FAQ)

°ìÈÌÅª¤Ê¼ÁÌä

°ìÈÌÅª¤Ê¼ÁÌä

1.1) PostgreSQL ¤È¤Ï²¿¤Ç¤¹¤«¡© ²¿¤ÈÆÉ¤ß¤Þ¤¹¤«¡©

1.2) PostgreSQL ¤ÎÃøºî¸¢¤Ï¤É¤¦¤Ê¤Ã¤Æ¤Þ¤¹¤«¡©

1.4) Unix°Ê³°¤Î°Ü¿¢ÈÇ¤Ç»È¤¨¤ë¤â¤Î¤Ï¡©

1.6) ¥µ¥Ý¡¼¥È¤Ï¤É¤³¤Ç¼õ¤±¤é¤ì¤Þ¤¹¤«¡©

1.11) PostgreSQL¤ÏÀ¾Îñ2000Ç¯ÌäÂê(Y2K)¤ËÂÐ±þ¤·¤Æ¤¤¤Þ¤¹¤«¡©

¥æ¡¼¥¶¡¼¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä

2.1) PostgreSQL ¤Î¤¿¤á¤Î ODBC ¥É¥é¥¤¥Ð¡¼¤Ï¤¢¤ê¤Þ¤¹¤«¡©

2.2) PostgreSQL ¤ò Web ¥Ú¡¼¥¸¤ÈÏ¢·È¤µ¤»¤ë¤Ë¤Ï¤É¤ó¤Ê¥Ä¡¼¥ë¤¬¤¢¤ê¤Þ¤¹¤«¡©

2.3) PostgreSQL ¤Ë¥°¥é¥Õ¥£¥«¥ë¡¦¥æ¡¼¥¶¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Ï¤¢¤ê¤Þ¤¹¤«¡©

2.4) ¤É¤Î¤è¤¦¤Ê¸À¸ì¤Ç PostgreSQL ¤ÈÄÌ¿®¤Ç¤­¤¹¤«¡©

´ÉÍý¾å¤Î¼ÁÌä

3.1) ¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð /usr/local/pgsql °Ê³°¤Î¾ì½ê¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¤«¡©

3.2) postmaster ¤òÁö¤é¤»¤ë¤È¡¢Bad System Call ¤È¤«¥³¥¢¡¦¥À¥ó¥×¤·¤¿¤È¤Î¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©

3.3) postmaster ¤òÁö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢IpcMemoryCreate ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©

3.4) postmaster¤òÁö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢IpcSemaphoreCreate ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©

3.5) Â¾¤Î¥Û¥¹¥È¤«¤é¤ÎÀÜÂ³¤Ï¤É¤Î¤è¤¦¤ËÀ©¸æ¤·¤Þ¤¹¤«¡©

3.6) ¤è¤êÎÉ¤¤À­Ç½¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥¨¥ó¥¸¥ó¤ò¤É¤Î¤è¤¦¤ËÄ´À°¤¹¤ì¤ÐÎÉ¤¤¤Ç¤¹¤«¡©

3.7) ¤É¤Î¤è¤¦¤Ê¥Ç¥Ð¥°µ¡Ç½¤¬»È¤¨¤Þ¤¹¤«¡©

3.8) ÀÜÂ³¤·¤è¤¦¤È¤¹¤ë¤È¤­¤Ë 'Sorry, too many clients' ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©

3.9) pgsql_tmp ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤Ë¤Ï²¿¤¬¤¢¤ê¤Þ¤¹¤«¡© +

3.9) pgsql_tmp ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤Ë¤Ï²¿¤¬¤¢¤ê¤Þ¤¹¤«¡©

3.10) PostgreSQL¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤ò¥¢¥Ã¥×¥Ç¡¼¥È¤¹¤ë¤Î¤Ë¥À¥ó¥×¤È¥ê¥¹¥È¥¢¤ò¤·¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©

3.11) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤ó¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©

Áàºî¾å¤Î¼ÁÌä

4.1) ¥Ð¥¤¥Ê¥ê¡¦¥«¡¼¥½¥ë¤ÈÄÌ¾ï¥«¡¼¥½¥ë¤È¤Î¸·Ì©¤Ê°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©

4.2) ºÇ½é¤Î¿ô¥í¥¦¤Î¤ß¤ò SELECT¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©¥é¥ó¥À¥à¤Ê¥í¥¦¡©

4.3) ¥Æ¡¼¥Ö¥ë¤ä¤½¤ÎÂ¾¤Î¾ðÊó¤Î¥ê¥¹¥È¤ò psql ¤Ç¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©

4.5) ¥í¥¦¡¢¥Æ¡¼¥Ö¥ë¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎºÇÂç¥µ¥¤¥º¤Ï¡©

4.6) °ìÈÌÅª¤Ê¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤«¤é¥Ç¡¼¥¿¤òÊÝÂ¸¤¹¤ë¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯ÍÆÎÌ¤Ï¤É¤Î¤¯¤é¤¤É¬Í×¤Ç¤¹¡©

4.7) ÄêµÁ¤µ¤ì¤¿¥Æ¡¼¥Ö¥ë¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¢¤ª¤è¤Ó¡¢¥æ¡¼¥¶¤ò¤É¤Î¤è¤¦¤Ë¤·¤Æ¸«¤Ä¤±½Ð¤·¤Þ¤¹¤«¡©

4.8) Ìä¤¤¹ç¤ï¤»¤¬ÃÙ¤¤¤¦¤¨¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤Ã¤Æ¤¤¤ëÍÍ»Ò¤¬¤¢¤ê¤Þ¤»¤ó¡£¤Ê¤¼¤Ç¤¹¤«¡©

4.9) Ìä¤¤¹ç¤ï¤»¥ª¥Ö¥Æ¥£¥Þ¥¤¥¶¤¬¤É¤Î¤è¤¦¤ËÌä¤¤¹ç¤ï¤»¤òÉ¾²Á¤¹¤ë¤Î¤«¤ò¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©

4.10) R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤È¤Ï²¿¤Ç¤¹¤«¡©

4.11) °äÅÁÅªÌä¤¤¹ç¤ï¤»ºÇÅ¬²½¤È¤Ï²¿¤Ç¤¹¤«¡©

4.13) Ìä¤¤¹ç¤ï¤»¤ÎÃæ¤Ç¡¢¥Õ¥£¡¼¥ë¥É¤¬ NULL ¤Ç¤¢¤ë¤³¤È¤ò¸¡½Ð¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©

4.14) ÍÍ¡¹¤ÊÊ¸»ú·¿¤Î¤½¤ì¤¾¤ì¤Î°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©

4.15.1) ÄÌÈÖ(serial)¡¿¼«Æ°ÁýÊ¬¥Õ¥£¡¼¥ë¥É¤Ï¤É¤Î¤è¤¦¤Ë¤Ä¤¯¤ê¤Þ¤¹¤«¡©

4.15.2) SERIAL¥Ç¡¼¥¿·¿¤ËÁÞÆþ¤µ¤ì¤ëÃÍ¤Ï¡¢¤É¤¦¤¹¤ì¤ÐÆÀ¤é¤ì¤Þ¤¹¤«¡©

PostgreSQL(¥Ý¥¹¥È¥°¥ì¥¹¡¦¥¥å¡¼¡¦¥¨¥ë)¤Ë¤Ä¤¤¤Æ¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤Î²òÅú(FAQ)

2.4) ¤É¤Î¤è¤¦¤Ê¸À¸ì¤Ç PostgreSQL ¤ÈÄÌ¿®¤Ç¤¤¹¤«¡©

3.1) ¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð /usr/local/pgsql °Ê³°¤Î¾ì½ê¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤¤Þ¤¹¤«¡©

3.6) ¤è¤êÎÉ¤¤ÀÇ½¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥¨¥ó¥¸¥ó¤ò¤É¤Î¤è¤¦¤ËÄ´À°¤¹¤ì¤ÐÎÉ¤¤¤Ç¤¹¤«¡©

3.8) ÀÜÂ³¤·¤è¤¦¤È¤¹¤ë¤È¤¤Ë 'Sorry, too many clients' ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©

4.6) °ìÈÌÅª¤Ê¥Æ¥¥¹¥È¥Õ¥¡¥¤¥ë¤«¤é¥Ç¡¼¥¿¤òÊÝÂ¸¤¹¤ë¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯ÍÆÎÌ¤Ï¤É¤Î¤¯¤é¤¤É¬Í×¤Ç¤¹¡©

4.15.4) ¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬ÃæÃÇ¤·¤¿¤È¤¤Ë¤â¤¦¤¤¤Á¤É¥·¡¼¥±¥ó¥¹ÈÖ¹æ¤¬»È¤ï¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©¥·¡¼¥±¥ó¥¹¡¿SERIAL¥«¥é¥à¤Ë¶õ¤¤¬¤¢¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©

4.24) Ê£¿ô¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»È¤¦Ìä¤¤¹ç¤ï¤»¤Ï¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð¤Ç¤¤Þ¤¹¤«¡©

4.26)¤Ê¤¼¡¢PL/PgSQL ´Ø¿ô¤ÎÃæ¤«¤é°ì»þ¥Æ¡¼¥Ö¥ë¤ò³Î¼Â¤Ë create/drop ¤¹¤ë¤³¤È¤¬¤Ç¤¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¤«¡©

5.3) ¥¿¥×¥ë¤òÊÖ¤¹ C¸À¸ì¤Î´Ø¿ô¤Ï¤É¤Î¤è¤¦¤Ë½ñ¤¤Þ¤¹¤«¡©
