From d5f6cfc72e17282a8286ef54e01abb2ef6eb303e Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 28 Nov 2003 20:20:33 +0000
Subject: [PATCH] Update Russian FAQ, both branches.
Viktor Vislobokov
---
doc/FAQ_russian | 38 ++++++++++++++++++++----------------
doc/src/FAQ/FAQ_russian.html | 37 ++++++++++++++++++-----------------
2 files changed, 40 insertions(+), 35 deletions(-)
diff --git a/doc/FAQ_russian b/doc/FAQ_russian
index f2a04acf0c..ff526bb66f 100644
--- a/doc/FAQ_russian
+++ b/doc/FAQ_russian
@@ -1,12 +1,12 @@
Otvety na chasto zadavaemye voprosy po PostgreSQL
- Data poslednego obnovleniya: Voskresen'e 5 Oktyabrya 10:25:21 EDT 2003
+ Data poslednego obnovleniya: Sreda 19 noyabrya 11:50:04 EDT 2003
Anglijskij variant soprovozhdaet: Bryus Mom'yan (Bruce Momjian)
(pgman@candle.pha.pa.us)
- Perevel na russkij: Viktor Vislobokov (victor_v@permonline.ru)
+ Perevel na russkij: Viktor Vislobokov (corochoone@perm.ru)
Samuyu svezhuyu anglijskuyu versiyu dokumenta mozhno najti na
http://www.PostgreSQL.org/docs/faqs/FAQ.html.
@@ -273,16 +273,17 @@
http://www.PostgreSQL.org
- Esche suschestvuet IRC kanal na EFNet i OpenProjects, s nazvaniem
+ Esche suschestvuet IRC kanal na EFNet i Freenode, s nazvaniem
#PostgreSQL. YA ispol'zuyu dlya podklyucheniya k `etomu kanalu komandu
- Unix irc -c '#PostgreSQL' "$USER" irc.phoenix.net.
+ Unix irc -c '#PostgreSQL' "$USER" irc.phoenix.net. ili irc -c
+ '#PostgreSQL' "$USER" irc.freenode.net.
Spisok kommercheskoj podderzhki kompanij dostupen na
http://techdocs.postgresql.org/companies.php.
1.7) Kakaya poslednyaya versiya?
- Poslednij vypusk PostgreSQL - `eto versiya 7.3.4.
+ Poslednij vypusk PostgreSQL - `eto versiya 7.4.
My planiruem vypuskat' novye versii kazhdye 6-8 mesyacev.
@@ -485,7 +486,7 @@
2.3) Est' li u PostgreSQL graficheskij interfejs pol'zovatelya?
Da, suschestvuet neskol'ko graficheskih interfejsov dlya PostgreSQL.
- `Eto PgAccess (http://www.pgaccess.org, PgAdmin II
+ `Eto PgAccess (http://www.pgaccess.org, PgAdmin III
(http://www.pgadmin.org, Win32-only), RHDB Admin (
http://sources.redhat.com/rhdb/) i Rekall (
http://www.thekompany.com/products/rekall/, kommercheskij). Takzhe
@@ -770,7 +771,7 @@ dalit'
Suschestvuyut sleduyuschie ogranicheniya:
Maksimal'nyj razmer bazy? neogranichen (suschestvuyut bazy na
-4 TB)
+32 TB)
Maksimal'nyj razmer tablicy? 32 TB
Maksimal'nyj razmer zapisi? 1.6 TB
Maksimal'nyj razmer polya? 1 GB
@@ -990,7 +991,7 @@ t' null-bajt bez opaski)
4.15.1) Kak mne sozdat' pole serial/s-avto-uvelicheniem?
PostgreSQL podderzhivaet tip dannyh SERIAL. On avtomaticheski sozdaet
- posledovatel'nost' i indeks dlya kolonki. Naprimer:
+ posledovatel'nost'. Naprimer:
CREATE TABLE person (
id SERIAL,
name TEXT
@@ -1002,7 +1003,6 @@ t' null-bajt bez opaski)
id INT4 NOT NULL DEFAULT nextval('person_id_seq'),
name TEXT
);
- CREATE UNIQUE INDEX person_id_key ON person ( id );
Smotrite podrobnosti o posledovatel'nostyah na stranice rukovodstva
posvyaschennoj create_sequence. Vy takzhe mozhete ispol'zovat' kazhdoe
@@ -1160,12 +1160,12 @@ CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
4.22) Pochemu moi podzaprosy, ispol'zuyuschie IN tak medlenno rabotaeyut?
- V nastoyaschij moment, my svyazyvaem pozaprosy dlya vneshnih zaprosov
- cherez posledovatel'nyj perebor rezul'tata podzaprosa dlya kazhdoj
- zapisi vneshnego zaprosa. Esli podzapros vozvraschaet tol'ko neskol'ko
- zapisej i vneshnij zapros vozvraschaet mnogo zapisej, IN rabotaet
- naibolee bystro. CHtoby uvelichit' skorost' v drugih zaprosah,
- zamenite IN na EXISTS:
+ V versiyah do 7.4, podzaprosy svyazyvalis' s roditel'skimi zaprosami
+ cherez posledovatel'nyj perebor rezul'tatov pozaprosa dlya kazhdoj
+ zapisi roditel'skogo zaprosa. Esli podzapros vozvraschaet tol'ko
+ neskol'ko zapisej, a roditel'skij zapros vozvraschaet mnogo zapisej,
+ IN rabotaet naibolee bystro. CHtoby uvelichit' skorost' v drugih
+ zaprosah, zamenite IN na EXISTS:
SELECT *
FROM tab
WHERE col IN (SELECT subcol FROM subtab);
@@ -1176,8 +1176,12 @@ CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
WHERE EXISTS (SELECT subcol FROM subtab WHERE subcol = col);
CHtoby takaya konstrukciya rabotala bystro, kolonka subcol dolzhna
- byt' proindeksirovana. `Eta problema proizvoditel'nosti budet
- ustranena v versii 7.4.
+ byt' proindeksirovana.
+
+ V versii 7.4 i vyshe, IN fakticheski ispol'zuet takoj zhe mehanizm
+ svyazyvaniya kak i obychnye zaprosy, po`etomu predpochtitel'nym
+ yavlyaetsya ispol'zovanie EXISTS
+ .
4.23) Kak mne vypolnit' vneshnee svyazyvanie?
diff --git a/doc/src/FAQ/FAQ_russian.html b/doc/src/FAQ/FAQ_russian.html
index 10658fff80..9c5bf192d7 100644
--- a/doc/src/FAQ/FAQ_russian.html
+++ b/doc/src/FAQ/FAQ_russian.html
@@ -9,17 +9,16 @@
PostgreSQL FAQ
-
+
ïÔ×ÅÔÙ ÎÁ ÞÁÓÔÏ ÚÁÄÁ×ÁÅÍÙÅ ×ÏÐÒÏÓÙ ÐÏ PostgreSQL
- äÁÔÁ ÐÏÓÌÅÄÎÅÇÏ ÏÂÎÏ×ÌÅÎÉÑ: ÷ÏÓËÒÅÓÅÎØÅ 5 ïËÔÑÂÒÑ 10:25:21 EDT 2003
+ äÁÔÁ ÐÏÓÌÅÄÎÅÇÏ ÏÂÎÏ×ÌÅÎÉÑ: óÒÅÄÁ 19 ÎÏÑÂÒÑ 11:50:04 EDT 2003
áÎÇÌÉÊÓËÉÊ ×ÁÒÉÁÎÔ ÓÏÐÒÏ×ÏÖÄÁÅÔ: âÒÀÓ íÏÍØÑÎ (Bruce Momjian) (pgman@candle.pha.pa.us)
ðÅÒÅ×ÅÌ ÎÁ ÒÕÓÓËÉÊ: ÷ÉËÔÏÒ ÷ÉÓÌÏÂÏËÏ× (victor_v@permonline.ru)
+ "mailto:pgman@candle.pha.pa.us">corochoone@perm.ru)
óÁÍÕÀ Ó×ÅÖÕÀ ÁÎÇÌÉÊÓËÕÀ ×ÅÒÓÉÀ ÄÏËÕÍÅÎÔÁ ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ
@@ -321,16 +320,17 @@
http://www.PostgreSQL.org
-
åÝÅ ÓÕÝÅÓÔ×ÕÅÔ IRC ËÁÎÁÌ ÎÁ EFNet É OpenProjects, Ó ÎÁÚ×ÁÎÉÅÍ
+
åÝÅ ÓÕÝÅÓÔ×ÕÅÔ IRC ËÁÎÁÌ ÎÁ EFNet É Freenode, Ó ÎÁÚ×ÁÎÉÅÍ
#PostgreSQL. ñ ÉÓÐÏÌØÚÕÀ ÄÌÑ ÐÏÄËÌÀÞÅÎÉÑ Ë ÜÔÏÍÕ ËÁÎÁÌÕ ËÏÍÁÎÄÕ Unix
- irc -c '#PostgreSQL' "$USER" irc.phoenix.net.
+ irc -c '#PostgreSQL' "$USER" irc.phoenix.net.
ÉÌÉ
+ irc -c '#PostgreSQL' "$USER" irc.freenode.net.
óÐÉÓÏË ËÏÍÍÅÒÞÅÓËÏÊ ÐÏÄÄÅÒÖËÉ ËÏÍÐÁÎÉÊ ÄÏÓÔÕÐÅÎ ÎÁ
http://techdocs.postgresql.org/companies.php.
1.7) ëÁËÁÑ ÐÏÓÌÅÄÎÑÑ ×ÅÒÓÉÑ?
- ðÏÓÌÅÄÎÉÊ ×ÙÐÕÓË PostgreSQL - ÜÔÏ ×ÅÒÓÉÑ 7.3.4.
+ ðÏÓÌÅÄÎÉÊ ×ÙÐÕÓË PostgreSQL - ÜÔÏ ×ÅÒÓÉÑ 7.4.
íÙ ÐÌÁÎÉÒÕÅÍ ×ÙÐÕÓËÁÔØ ÎÏ×ÙÅ ×ÅÒÓÉÉ ËÁÖÄÙÅ 6-8 ÍÅÓÑÃÅ×.
@@ -566,7 +566,7 @@
äÁ, ÓÕÝÅÓÔ×ÕÅÔ ÎÅÓËÏÌØËÏ ÇÒÁÆÉÞÅÓËÉÈ ÉÎÔÅÒÆÅÊÓÏ× ÄÌÑ PostgreSQL.
üÔÏ PgAccess (http://www.pgaccess.org,
- PgAdmin II (http://www.pgadmin.org,
+ PgAdmin III (http://www.pgadmin.org,
Win32-only), RHDB Admin (
http://sources.redhat.com/rhdb/) É Rekall
(
@@ -885,7 +885,7 @@
óÕÝÅÓÔ×ÕÀÔ ÓÌÅÄÕÀÝÉÅ ÏÇÒÁÎÉÞÅÎÉÑ:
- íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÂÁÚÙ? ÎÅÏÇÒÁÎÉÞÅÎ (ÓÕÝÅÓÔ×ÕÀÔ ÂÁÚÙ ÎÁ 4 TB)
+ íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÂÁÚÙ? ÎÅÏÇÒÁÎÉÞÅÎ (ÓÕÝÅÓÔ×ÕÀÔ ÂÁÚÙ ÎÁ 32 TB)
íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÔÁÂÌÉÃÙ? 32 TB
íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÚÁÐÉÓÉ? 1.6 TB
íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÐÏÌÑ? 1 GB
@@ -1122,8 +1122,7 @@ BYTEA bytea
serial/Ó-Á×ÔÏ-Õ×ÅÌÉÞÅÎÉÅÍ?
PostgreSQL ÐÏÄÄÅÒÖÉ×ÁÅÔ ÔÉÐ ÄÁÎÎÙÈ SERIAL. ïÎ
- Á×ÔÏÍÁÔÉÞÅÓËÉ ÓÏÚÄÁÅÔ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ É ÉÎÄÅËÓ ÄÌÑ ËÏÌÏÎËÉ.
- îÁÐÒÉÍÅÒ:
+ Á×ÔÏÍÁÔÉÞÅÓËÉ ÓÏÚÄÁÅÔ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ. îÁÐÒÉÍÅÒ:
CREATE TABLE person (
id SERIAL,
@@ -1138,7 +1137,6 @@ BYTEA bytea
id INT4 NOT NULL DEFAULT nextval('person_id_seq'),
name TEXT
);
- CREATE UNIQUE INDEX person_id_key ON person ( id );
óÍÏÔÒÉÔÅ ÐÏÄÒÏÂÎÏÓÔÉ Ï ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÑÈ ÎÁ ÓÔÒÁÎÉÃÅ ÒÕËÏ×ÏÄÓÔ×Á
@@ -1334,10 +1332,10 @@ BYTEA bytea
4.22) ðÏÞÅÍÕ ÍÏÉ ÐÏÄÚÁÐÒÏÓÙ, ÉÓÐÏÌØÚÕÀÝÉÅ
IN
ÔÁË ÍÅÄÌÅÎÎÏ ÒÁÂÏÔÁÅÀÔ?
- ÷ ÎÁÓÔÏÑÝÉÊ ÍÏÍÅÎÔ, ÍÙ Ó×ÑÚÙ×ÁÅÍ ÐÏÚÁÐÒÏÓÙ ÄÌÑ ×ÎÅÛÎÉÈ ÚÁÐÒÏÓÏ×
- ÞÅÒÅÚ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÅÒÅÂÏÒ ÒÅÚÕÌØÔÁÔÁ ÐÏÄÚÁÐÒÏÓÁ ÄÌÑ ËÁÖÄÏÊ
- ÚÁÐÉÓÉ ×ÎÅÛÎÅÇÏ ÚÁÐÒÏÓÁ. åÓÌÉ ÐÏÄÚÁÐÒÏÓ ×ÏÚ×ÒÁÝÁÅÔ ÔÏÌØËÏ ÎÅÓËÏÌØËÏ
- ÚÁÐÉÓÅÊ É ×ÎÅÛÎÉÊ ÚÁÐÒÏÓ ×ÏÚ×ÒÁÝÁÅÔ ÍÎÏÇÏ ÚÁÐÉÓÅÊ,
+
÷ ×ÅÒÓÉÑÈ ÄÏ 7.4, ÐÏÄÚÁÐÒÏÓÙ Ó×ÑÚÙ×ÁÌÉÓØ Ó ÒÏÄÉÔÅÌØÓËÉÍÉ ÚÁÐÒÏÓÁÍÉ
+ ÞÅÒÅÚ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÅÒÅÂÏÒ ÒÅÚÕÌØÔÁÔÏ× ÐÏÚÁÐÒÏÓÁ ÄÌÑ ËÁÖÄÏÊ
+ ÚÁÐÉÓÉ ÒÏÄÉÔÅÌØÓËÏÇÏ ÚÁÐÒÏÓÁ. åÓÌÉ ÐÏÄÚÁÐÒÏÓ ×ÏÚ×ÒÁÝÁÅÔ ÔÏÌØËÏ ÎÅÓËÏÌØËÏ
+ ÚÁÐÉÓÅÊ, Á ÒÏÄÉÔÅÌØÓËÉÊ ÚÁÐÒÏÓ ×ÏÚ×ÒÁÝÁÅÔ ÍÎÏÇÏ ÚÁÐÉÓÅÊ,
IN
ÒÁÂÏÔÁÅÔ ÎÁÉÂÏÌÅÅ ÂÙÓÔÒÏ. þÔÏÂÙ
Õ×ÅÌÉÞÉÔØ ÓËÏÒÏÓÔØ × ÄÒÕÇÉÈ ÚÁÐÒÏÓÁÈ, ÚÁÍÅÎÉÔÅ IN
ÎÁ
EXISTS
:
@@ -1355,8 +1353,11 @@ BYTEA bytea
þÔÏÂÙ ÔÁËÁÑ ËÏÎÓÔÒÕËÃÉÑ ÒÁÂÏÔÁÌÁ ÂÙÓÔÒÏ, ËÏÌÏÎËÁ subcol
- ÄÏÌÖÎÁ ÂÙÔØ ÐÒÏÉÎÄÅËÓÉÒÏ×ÁÎÁ. üÔÁ ÐÒÏÂÌÅÍÁ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ ÂÕÄÅÔ
- ÕÓÔÒÁÎÅÎÁ × ×ÅÒÓÉÉ 7.4.
+ ÄÏÌÖÎÁ ÂÙÔØ ÐÒÏÉÎÄÅËÓÉÒÏ×ÁÎÁ.
+
+ ÷ ×ÅÒÓÉÉ 7.4 É ×ÙÛÅ, IN
ÆÁËÔÉÞÅÓËÉ ÉÓÐÏÌØÚÕÅÔ ÔÁËÏÊ ÖÅ
+ ÍÅÈÁÎÉÚÍ Ó×ÑÚÙ×ÁÎÉÑ ËÁË É ÏÂÙÞÎÙÅ ÚÁÐÒÏÓÙ, ÐÏÜÔÏÍÕ ÐÒÅÄÐÏÞÔÉÔÅÌØÎÙÍ
+ Ñ×ÌÑÅÔÓÑ ÉÓÐÏÌØÚÏ×ÁÎÉÅ EXISTS
.
4.23) ëÁË ÍÎÅ ×ÙÐÏÌÎÉÔØ ×ÎÅÛÎÅÅ Ó×ÑÚÙ×ÁÎÉÅ?
--
2.49.0