Обсуждение: Updated Russian translation of FAQ
Hello.
There is update Russian translation of FAQ in attachment.
2 Bruce:
a) IMHO this is not full correctly for understanding:
If a table is created <SMALL>WITH OIDS</SMALL>, each row gets a unique a <SMALL>OID</SMALL>. O<SMALL>ID</SMALL>s are
automatically assigned unique 4-byte integers that are unique across the entire installation. However, they overflow at 4 billion, and then
the O<SMALL>ID</SMALL>s start being duplicated.
How OID can be "UNIQUE acrcoss ENTIRE INSTALLATION" and in same time "then OID start being DUPLICATED"? IMHO there two mutually exclusive facts.
b) May be, this need to make more exact?
Other machines will not be able to connect unless you modify listen_addresses in the postgresql.conf file, enable host-based authentication by modifying the $PGDATA/pg_hba.conf file, and restart the server.
In previous versions of FAQ, was: "postmaster" instead "server". Now, It will be confuse: What is server? Database server or computer?
There is update Russian translation of FAQ in attachment.
2 Bruce:
a) IMHO this is not full correctly for understanding:
If a table is created <SMALL>WITH OIDS</SMALL>, each row gets a unique a <SMALL>OID</SMALL>. O<SMALL>ID</SMALL>s are
automatically assigned unique 4-byte integers that are unique across the entire installation. However, they overflow at 4 billion, and then
the O<SMALL>ID</SMALL>s start being duplicated.
How OID can be "UNIQUE acrcoss ENTIRE INSTALLATION" and in same time "then OID start being DUPLICATED"? IMHO there two mutually exclusive facts.
b) May be, this need to make more exact?
Other machines will not be able to connect unless you modify listen_addresses in the postgresql.conf file, enable host-based authentication by modifying the $PGDATA/pg_hba.conf file, and restart the server.
In previous versions of FAQ, was: "postmaster" instead "server". Now, It will be confuse: What is server? Database server or computer?
Вложения
Виктор Вислобоков wrote: > How OID can be "UNIQUE acrcoss ENTIRE INSTALLATION" and in same time > "then OID start being DUPLICATED"? IMHO there two mutually exclusive facts. > "unique across database cluster"? > Other machines will not be able to connect unless you modify > /listen_addresses/ in the /postgresql.conf/ file, enable host-based > authentication by modifying the /$PGDATA/pg_hba.conf/ file, and restart > the server. > "... and restart the PostgreSQL server"? -- Euler Taveira de Oliveira http://www.timbira.com/
> How OID can be "UNIQUE acrcoss ENTIRE INSTALLATION" and in same time
> "then OID start being DUPLICATED"? IMHO there two mutually exclusive facts.
>
"unique across database cluster"?
If you are right, OID can be duplicated across database cluster too, in case big database. May be, I'm wrong. Bruce, what you think?
> Other machines will not be able to connect unless you modify
> /listen_addresses/ in the /postgresql.conf/ file, enable host-based
> authentication by modifying the /$PGDATA/pg_hba.conf/ file, and restart
> the server.
>
"... and restart the PostgreSQL server"?
Yes, this more exactly.
With best wishes,
Viktor Vislobokov
St.Peterburg, Russia.
=?KOI8-R?B?98nL1M/SIPfJ08zPws/Lz9c=?= wrote: > Hello. > > There is update Russian translation of FAQ in attachment. > > > 2 Bruce: > > a) IMHO this is not full correctly for understanding: > > If a table is created <SMALL>WITH OIDS</SMALL>, each row gets a unique a > <SMALL>OID</SMALL>. O<SMALL>ID</SMALL>s are > automatically assigned unique 4-byte integers that are unique across the > entire installation. However, they overflow at 4 billion, and then > the O<SMALL>ID</SMALL>s start being duplicated. > > How OID can be "UNIQUE acrcoss ENTIRE INSTALLATION" and in same time "then > OID start being DUPLICATED"? IMHO there two mutually exclusive facts. They are unique _until_ they overflow. > b) May be, this need to make more exact? > > Other machines will not be able to connect unless you modify * > listen_addresses* in the *postgresql.conf* file, enable host-based > authentication by modifying the *$PGDATA/pg_hba.conf* file, and restart the > server. > > In previous versions of FAQ, was: "postmaster" instead "server". Now, It > will be confuse: What is server? Database server or computer? Agreed, I changed it to mention "database server". -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Patch applied. Thanks. The web site version will update shortly. --------------------------------------------------------------------------- =?KOI8-R?B?98nL1M/SIPfJ08zPws/Lz9c=?= wrote: > Hello. > > There is update Russian translation of FAQ in attachment. > > > 2 Bruce: > > a) IMHO this is not full correctly for understanding: > > If a table is created <SMALL>WITH OIDS</SMALL>, each row gets a unique a > <SMALL>OID</SMALL>. O<SMALL>ID</SMALL>s are > automatically assigned unique 4-byte integers that are unique across the > entire installation. However, they overflow at 4 billion, and then > the O<SMALL>ID</SMALL>s start being duplicated. > > How OID can be "UNIQUE acrcoss ENTIRE INSTALLATION" and in same time "then > OID start being DUPLICATED"? IMHO there two mutually exclusive facts. > > b) May be, this need to make more exact? > > Other machines will not be able to connect unless you modify * > listen_addresses* in the *postgresql.conf* file, enable host-based > authentication by modifying the *$PGDATA/pg_hba.conf* file, and restart the > server. > > In previous versions of FAQ, was: "postmaster" instead "server". Now, It > will be confuse: What is server? Database server or computer? [ Attachment, skipping... ] -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +