Skip to content

P
Postgres FD Implementation
Commit d5f6cfc7 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Update Russian FAQ, both branches. 

Viktor Vislobokov
parent 3c0ddc58
Show whitespace changes
Inline Side-by-side
Showing with 40 additions and 35 deletions
doc/FAQ_russian
View file @ d5f6cfc7
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?
......
doc/src/FAQ/FAQ_russian.html
View file @ d5f6cfc7
......@@ -9,17 +9,16 @@
<TITLE>PostgreSQL FAQ</TITLE>
</HEAD>
<BODY bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000"
alink="#0000ff">
<BODY bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000" alink="#0000ff">
<H1> PostgreSQL</H1>
<P> : 5 10:25:21 EDT 2003</P>
<P> : 19 11:50:04 EDT 2003</P>
<P> : (Bruce Momjian) (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
</P>
<P> : (<A href=
"mailto:pgman@candle.pha.pa.us">victor_v@permonline.ru</A>)<BR>
"mailto:pgman@candle.pha.pa.us">corochoone@perm.ru</A>)<BR>
</P>
<P>
......@@ -321,16 +320,17 @@
<A href="http://www.PostgreSQL.org">http://www.PostgreSQL.org</A>
</BLOCKQUOTE>
<P> IRC EFNet OpenProjects,
<P> IRC EFNet Freenode,
<I>#PostgreSQL</I>. Unix
<CODE>irc -c '#PostgreSQL' "$USER" irc.phoenix.net.</CODE></P>
<CODE>irc -c '#PostgreSQL' "$USER" irc.phoenix.net.</CODE>
<CODE>irc -c '#PostgreSQL' "$USER" irc.freenode.net.</CODE></P>
<P>
<A href="http://techdocs.postgresql.org/companies.php">http://techdocs.postgresql.org/companies.php</A>.</P>
<H4><A name="1.7">1.7</A>) ?</H4>
<P> PostgreSQL - 7.3.4.</P>
<P> PostgreSQL - 7.4.</P>
<P> 6-8 .</P>
......@@ -566,7 +566,7 @@
<P>, PostgreSQL.
PgAccess (<A href="http://www.pgaccess.org/">http://www.pgaccess.org</A>,
PgAdmin II (<A href="http://www.pgadmin.org/">http://www.pgadmin.org</A>,
PgAdmin III (<A href="http://www.pgadmin.org/">http://www.pgadmin.org</A>,
Win32-only), RHDB Admin (<A href="http://sources.redhat.com/rhdb/">
http://sources.redhat.com/rhdb/</A>) Rekall
(<A href="http://www.thekompany.com/products/rekall/">
......@@ -885,7 +885,7 @@
<P> :</P>
<PRE>
? ( 4 TB)
? ( 32 TB)
? 32 TB
? 1.6 TB
? 1 GB
......@@ -1122,8 +1122,7 @@ BYTEA bytea
serial/--?</H4>
<P>PostgreSQL <SMALL>SERIAL</SMALL>.
.
:</P>
. :</P>
<PRE>
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 );
</PRE>
......@@ -1334,10 +1332,10 @@ BYTEA bytea
<H4><A name="4.22">4.22</A>) ,
<CODE><SMALL>IN</SMALL></CODE> ?</H4>
<P> ,
.
,
<P> 7.4,
.
, ,
<CODE><SMALL>IN</SMALL></CODE> .
, <CODE>IN</CODE>
<CODE>EXISTS</CODE>:</P>
......@@ -1355,8 +1353,11 @@ BYTEA bytea
</PRE>
, <CODE>subcol</CODE>
.
7.4.
.
<P> 7.4 , <CODE>IN</CODE>
,
<CODE>EXISTS</CODE></P>.
<H4><A name="4.23">4.23</A>) ?</H4>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment