mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-02-17 19:30:00 +08:00
Backpatch FAQs to 8.1.X.
This commit is contained in:
Bruce Momjian
parent
7cec8b4e4a
commit
61c91fd2d2
59
doc/FAQ
59
doc/FAQ
@ -1,9 +1,9 @@
|
||||
|
||||
Frequently Asked Questions (FAQ) for PostgreSQL
|
||||
|
||||
Last updated: Thu May 18 23:52:32 EDT 2006
|
||||
Last updated: Mon Oct 9 20:28:14 EDT 2006
|
||||
|
||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
||||
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
||||
|
||||
The most recent version of this document can be viewed at
|
||||
http://www.postgresql.org/files/documentation/faqs/FAQ.html.
|
||||
@ -19,7 +19,7 @@
|
||||
1.3) What is the copyright of PostgreSQL?
|
||||
1.4) What platforms does PostgreSQL support?
|
||||
1.5) Where can I get PostgreSQL?
|
||||
1.6) What is the latest release?
|
||||
1.6) What is the most recent release?
|
||||
1.7) Where can I get support?
|
||||
1.8) How do I submit a bug report?
|
||||
1.9) How do I find out about known bugs or missing features?
|
||||
@ -42,8 +42,7 @@
|
||||
3.3) How do I tune the database engine for better performance?
|
||||
3.4) What debugging features are available?
|
||||
3.5) Why do I get "Sorry, too many clients" when trying to connect?
|
||||
3.6) Why do I need to do a dump and restore to upgrade PostgreSQL
|
||||
releases?
|
||||
3.6 What is the upgrade process for PostgreSQL?
|
||||
3.7) What computer hardware should I use?
|
||||
|
||||
Operational Questions
|
||||
@ -153,8 +152,8 @@
|
||||
time of release are listed in the installation instructions.
|
||||
|
||||
PostgreSQL also runs natively on Microsoft Windows NT-based operating
|
||||
systems like Win2000, WinXP, and Win2003. A prepackaged installer is
|
||||
available at http://pgfoundry.org/projects/pginstaller. MSDOS-based
|
||||
systems like Win2000 SP4, WinXP, 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.
|
||||
|
||||
@ -168,7 +167,7 @@
|
||||
Via web browser, use http://www.postgresql.org/ftp/, and via ftp, use
|
||||
ftp://ftp.PostgreSQL.org/pub/.
|
||||
|
||||
1.6) What is the latest release?
|
||||
1.6) What is the most recent release?
|
||||
|
||||
The latest release of PostgreSQL is version 8.1.5.
|
||||
|
||||
@ -189,7 +188,7 @@
|
||||
(#postgresqlfr). There is also a PostgreSQL channel on EFNet.
|
||||
|
||||
A list of commercial support companies is available at
|
||||
http://techdocs.postgresql.org/companies.php.
|
||||
http://www.postgresql.org/support/professional_support.
|
||||
|
||||
1.8) How do I submit a bug report?
|
||||
|
||||
@ -350,8 +349,9 @@
|
||||
|
||||
2.3) Does PostgreSQL have a graphical user interface?
|
||||
|
||||
Yes, see http://techdocs.postgresql.org/guides/GUITools for a detailed
|
||||
list.
|
||||
There are a large number of GUI Tools that are available for
|
||||
PostgreSQL from both commercial and open source developers. A detailed
|
||||
list can be found in the PostgreSQL Community Documentation
|
||||
_________________________________________________________________
|
||||
|
||||
Administrative Questions
|
||||
@ -397,8 +397,9 @@
|
||||
|
||||
Hardware Selection
|
||||
The effect of hardware on performance is detailed in
|
||||
http://candle.pha.pa.us/main/writings/pgsql/hw_performance/inde
|
||||
x.html and http://www.powerpostgresql.com/PerfList/.
|
||||
http://www.powerpostgresql.com/PerfList/ and
|
||||
http://momjian.us/main/writings/pgsql/hw_performance/index.html
|
||||
.
|
||||
|
||||
3.4) What debugging features are available?
|
||||
|
||||
@ -413,16 +414,22 @@
|
||||
processes it can start by changing the max_connections value in
|
||||
postgresql.conf and restarting the postmaster.
|
||||
|
||||
3.6) Why do I need to do a dump and restore to upgrade between major
|
||||
PostgreSQL releases?
|
||||
3.6) What is the upgrade process for PostgreSQL?
|
||||
|
||||
The PostgreSQL team makes only small changes between minor releases,
|
||||
so upgrading from 7.4.0 to 7.4.1 does not require a dump and restore.
|
||||
However, major releases (e.g. from 7.3 to 7.4) often change the
|
||||
internal format of system tables and data files. These changes are
|
||||
often complex, so we don't maintain backward compatibility for data
|
||||
files. A dump outputs data in a generic format that can then be loaded
|
||||
in using the new internal format.
|
||||
The PostgreSQL team makes only bug fixes in minor releases, so, for
|
||||
example, upgrading from 7.4.8 to 7.4.9 does not require a dump and
|
||||
restore; merely stop the database server, install the updated
|
||||
binaries, and restart the server.
|
||||
|
||||
All users should upgrade to the most recent minor release as soon as
|
||||
it is available. While every upgrade has some risk, PostgreSQL minor
|
||||
releases are designed to fix only common bugs with the least risk. The
|
||||
community considers not upgrading more risky that upgrading.
|
||||
|
||||
Major releases (e.g. from 7.3 to 7.4) often change the internal format
|
||||
of system tables and data files. These changes are often complex, so
|
||||
we don't maintain backward compatibility for data files. A dump/reload
|
||||
of the database is required for major upgrades.
|
||||
|
||||
3.7) What computer hardware should I use?
|
||||
|
||||
@ -513,7 +520,7 @@
|
||||
|
||||
One limitation is that indexes can not be created on columns longer
|
||||
than about 2,000 characters. Fortunately, such indexes are rarely
|
||||
needed. Uniqueness is best guaranteed by a funtion index of an MD5
|
||||
needed. Uniqueness is best guaranteed by a function index of an MD5
|
||||
hash of the long column, and full text indexing allows for searching
|
||||
of words within the column.
|
||||
|
||||
@ -614,8 +621,8 @@
|
||||
FROM tab
|
||||
WHERE lower(col) = 'abc';
|
||||
|
||||
This will not use an standard index. However, if you create a
|
||||
expresssion index, it will be used:
|
||||
This will not use an standard index. However, if you create an
|
||||
expression index, it will be used:
|
||||
CREATE INDEX tabindex ON tab (lower(col));
|
||||
|
||||
If the above index is created as UNIQUE, though the column can store
|
||||
@ -720,7 +727,7 @@
|
||||
4.12) What is an OID? What is a CTID?
|
||||
|
||||
Every row that is created in PostgreSQL gets a unique OID unless
|
||||
created WITHOUT OIDS. OIDs are autotomatically assigned unique 4-byte
|
||||
created WITHOUT OIDS. OIDs are automatically assigned unique 4-byte
|
||||
integers that are unique across the entire installation. However, they
|
||||
overflow at 4 billion, and then the OIDs start being duplicated.
|
||||
PostgreSQL uses OIDs to link its internal system tables together.
|
||||
|
||||
111
doc/FAQ_AIX
111
doc/FAQ_AIX
@ -1,5 +1,5 @@
|
||||
From: Zeugswetter Andreas <ZeugswetterA@spardat.at>
|
||||
$Date: 2006/05/19 03:57:17 $
|
||||
$Date: 2006/10/10 00:29:13 $
|
||||
|
||||
On AIX 4.3.2 PostgreSQL compiled with the native IBM compiler xlc
|
||||
(vac.C 5.0.1) passes all regression tests. Other versions of OS and
|
||||
@ -365,3 +365,112 @@ References and resources
|
||||
IBM Redbook
|
||||
http://www.redbooks.ibm.com/redbooks/pdfs/sg245674.pdf
|
||||
http://www.redbooks.ibm.com/abstracts/sg245674.html?Open
|
||||
|
||||
|
||||
Statistics Collector Fun on AIX
|
||||
--------------------------------
|
||||
|
||||
When implementing PostgreSQL version 8.1 on AIX 5.3, we periodically
|
||||
ran into problems where the statistics collector would "mysteriously"
|
||||
not come up successfully.
|
||||
|
||||
This appears to be the result of unexpected behaviour in the IPv6
|
||||
implementation. It looks like PostgreSQL and IPv6 do not play very
|
||||
well together at this time on AIX.
|
||||
|
||||
Any of the following actions "fix" the problem.
|
||||
|
||||
1. Delete the localhost ipv6 address
|
||||
|
||||
(as root)
|
||||
# ifconfig lo0 inet6 ::1/0 delete
|
||||
|
||||
2. Remove IPv6 from net services. The file /etc/netsvc.conf, on AIX,
|
||||
is roughly equivalent to /etc/nsswitch.conf on Solaris/Linux.
|
||||
|
||||
The default, on AIX, is thus:
|
||||
|
||||
hosts=local,bind
|
||||
|
||||
Replace this with:
|
||||
|
||||
hosts=local4,bind4
|
||||
|
||||
to deactivate searching for IPv6 addresses.
|
||||
|
||||
|
||||
Shared Linking
|
||||
--------------
|
||||
|
||||
Shared libraries in AIX are different from shared libraries in Linux.
|
||||
|
||||
A shared library on AIX is an 'ar' archive containing shared objects. A
|
||||
shared object is produced by the linker when invoked appropriately (e.g.
|
||||
with -G), it is what we call a shared library on Linux.
|
||||
|
||||
-> On AIX, you can do a static as well as a dynamic
|
||||
-> link against a shared library, it depends on how you
|
||||
-> invoke the linker.
|
||||
|
||||
When you link statically, the shared objects from the library are added
|
||||
to your executable as required; when you link dynamically, only
|
||||
references to the shared objects are included in the executable.
|
||||
|
||||
Consequently you do not need a separate static library on AIX if you
|
||||
have a dynamic library.
|
||||
|
||||
However, you CAN have static libraries (ar archives containing *.o
|
||||
files), and the linker will link against them. This will of course
|
||||
always be a static link.
|
||||
|
||||
When the AIX linker searches for libraries to link, it will look for a
|
||||
library libxy.a as well as for a single shared object libxy.so when you
|
||||
tell it to -lyx. When it finds both in the same directory, it will
|
||||
prefer libpq.a unless invoked with -brtl.
|
||||
|
||||
This is where the problem occurs:
|
||||
|
||||
By default, PostgreSQL will (in the Linux way) create a shared object
|
||||
libpq.so and a static library libpq.a in the same directory.
|
||||
|
||||
Up to now, since the linker was invoked without the -brtl flag, linking
|
||||
on AIX was always static, as the linker preferred libpq.a over libpq.so.
|
||||
|
||||
We could have solved the problem by linking with -brtl on AIX, but we
|
||||
chose to go a more AIX-conforming way so that third party programs
|
||||
linking against PostgreSQL libraries will not be fooled into linking
|
||||
statically by default.
|
||||
|
||||
The 'new way' on AIX is:
|
||||
- Create libxy.so.n as before from the static library
|
||||
libxy.a with the linker.
|
||||
- Remove libxy.a
|
||||
- Recreate libxy.a as a dynamic library with
|
||||
ar -cr libxy.a libxy.so.n
|
||||
- Only install libxy.a, do not install libxy.so
|
||||
|
||||
Since linking is dynamic on AIX now, we have a new problem:
|
||||
|
||||
We must make sure that the executable finds its library even if the
|
||||
library is not installed in one of the standard library paths (/usr/lib
|
||||
or /lib).
|
||||
|
||||
On Linux this is done with an RPATH, on AIX the equivalent is LIBPATH
|
||||
that can be specified at link time with -blibpath:<colon separated path>
|
||||
. If you do not specify the LIBPATH, it is automatically computed from
|
||||
the -L arguments given to the linker. The LIBPATH, when set, must
|
||||
contain ALL directories where shared libraries should be searched,
|
||||
including the standard library directories.
|
||||
|
||||
Makefile.aix has been changed to link executables with a LIBPATH that
|
||||
contains --libdir when PostgreSQL is configured with --enable-rpath (the
|
||||
default).
|
||||
|
||||
The AIX equivalent for the Linux environment variable LD_LIBRARY_PATH is
|
||||
LIBPATH.
|
||||
|
||||
The regression tests rely on LD_LIBRARY_PATH and have to be changed to
|
||||
set LIBPATH as well.
|
||||
|
||||
Laurenz Albe
|
||||
|
||||
|
||||
54
doc/FAQ_DEV
54
doc/FAQ_DEV
@ -1,9 +1,9 @@
|
||||
|
||||
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
|
||||
|
||||
Last updated: Fri May 5 05:51:42 EDT 2006
|
||||
Last updated: Wed Sep 6 20:12:13 EDT 2006
|
||||
|
||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
||||
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
||||
|
||||
The most recent version of this document can be viewed at
|
||||
http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html.
|
||||
@ -125,7 +125,7 @@ General Questions
|
||||
3. The patch should be generated in contextual diff format (diff -c
|
||||
and should be applicable from the root directory. If you are
|
||||
unfamiliar with this, you might find the script
|
||||
src/tools/makediff/difforig useful. (Unified diffs are only
|
||||
src/tools/make_diff/difforig useful. (Unified diffs are only
|
||||
preferable if the file changes are single-line changes and do not
|
||||
rely on surrounding lines.)
|
||||
4. PostgreSQL is licensed under a BSD license, so any submissions
|
||||
@ -141,7 +141,7 @@ General Questions
|
||||
7. New feature patches should also be accompanied by documentation
|
||||
patches. If you need help checking the SQL standard, see 1.16.
|
||||
8. If you are adding a new feature, confirm that it has been tested
|
||||
thoughly. Try to test the feature in all conceivable scenarios.
|
||||
thoroughly. Try to test the feature in all conceivable scenarios.
|
||||
9. If it is a performance patch, please provide confirming test
|
||||
results to show the benefit of your patch. It is OK to post
|
||||
patches without this information, though the patch will not be
|
||||
@ -159,7 +159,8 @@ General Questions
|
||||
|
||||
Other than documentation in the source tree itself, you can find some
|
||||
papers/presentations discussing the code at
|
||||
http://www.postgresql.org/developer.
|
||||
http://www.postgresql.org/developer. An excellent presentation is at
|
||||
http://neilconway.org/talks/hacking/
|
||||
|
||||
1.7) How do I download/update the current source tree?
|
||||
|
||||
@ -276,9 +277,9 @@ General Questions
|
||||
applied to the distribution. This produces context diffs, which is our
|
||||
preferred format.
|
||||
|
||||
Our standard format is to indent each code level with one tab, where
|
||||
each tab is four spaces. You will need to set your editor to display
|
||||
tabs as four spaces:
|
||||
Our standard format BSD style, with each level of code indented one
|
||||
tab, where each tab is four spaces. You will need to set your editor
|
||||
or file viewer to display tabs as four spaces:
|
||||
vi in ~/.exrc:
|
||||
set tabstop=4
|
||||
set sw=4
|
||||
@ -286,40 +287,11 @@ General Questions
|
||||
more -x4
|
||||
less:
|
||||
less -x4
|
||||
emacs:
|
||||
M-x set-variable tab-width
|
||||
|
||||
or
|
||||
|
||||
(c-add-style "pgsql"
|
||||
'("bsd"
|
||||
(indent-tabs-mode . t)
|
||||
(c-basic-offset . 4)
|
||||
(tab-width . 4)
|
||||
(c-offsets-alist .
|
||||
((case-label . +)))
|
||||
)
|
||||
nil ) ; t = set this style, nil = don't
|
||||
|
||||
(defun pgsql-c-mode ()
|
||||
(c-mode)
|
||||
(c-set-style "pgsql")
|
||||
)
|
||||
|
||||
and add this to your autoload list (modify file path in macro):
|
||||
|
||||
(setq auto-mode-alist
|
||||
(cons '("\\`/home/andrew/pgsql/.*\\.[chyl]\\'" . pgsql-c-mode)
|
||||
auto-mode-alist))
|
||||
or
|
||||
/*
|
||||
* Local variables:
|
||||
* tab-width: 4
|
||||
* c-indent-level: 4
|
||||
* c-basic-offset: 4
|
||||
* End:
|
||||
*/
|
||||
|
||||
The tools/editors directory of the latest sources contains sample
|
||||
settings that can be used with the emacs, xemacs and vim editors, that
|
||||
assist in keeping to PostgreSQL coding standards.
|
||||
|
||||
pgindent will the format code by specifying flags to your operating
|
||||
system's utility indent. This article describes the value of a
|
||||
consistent coding style.
|
||||
|
||||
18
doc/FAQ_HPUX
18
doc/FAQ_HPUX
@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL 7.3
|
||||
HP-UX Specific
|
||||
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
|
||||
=======================================================
|
||||
last updated: $Date: 2004/09/02 17:46:24 $
|
||||
last updated: $Date: 2006/10/10 00:29:14 $
|
||||
|
||||
current maintainer: Tom Lane (tgl@sss.pgh.pa.us)
|
||||
original author: Tom Lane (tgl@sss.pgh.pa.us)
|
||||
@ -84,19 +84,3 @@ low-order-digit differences in the geometry tests, which vary depending
|
||||
on which compiler and math library versions you use.
|
||||
|
||||
Any other error is cause for suspicion.
|
||||
|
||||
The parallel regression test script (gmake check) is known to lock up
|
||||
on PA-RISC when run under HP's Bourne shells: /usr/bin/sh and
|
||||
/sbin/sh. To fix this problem, you will need PHCO_30269 with its
|
||||
dependent patch or successor patches:
|
||||
|
||||
PHCO_30269 s700_800 cumulative sh-posix(1) patch
|
||||
PHCO_29816 s700_800 rc(1M) scripts cumulative patch
|
||||
|
||||
To work around this problem, use ksh to run the regression script:
|
||||
|
||||
gmake SHELL=/bin/ksh check
|
||||
|
||||
If you see that the tests have stopped making progress and only a shell
|
||||
process is consuming CPU, kill the shell process and start over with the
|
||||
above command.
|
||||
|
||||
164
doc/FAQ_Solaris
164
doc/FAQ_Solaris
@ -1,11 +1,9 @@
|
||||
============================================================
|
||||
Frequently Asked Questions (FAQ) for PostgreSQL
|
||||
Sun Solaris specific
|
||||
to be read in conjunction with the installation instructions
|
||||
To be read in conjunction with the installation instructions.
|
||||
============================================================
|
||||
last updated: $Date: 2003/10/09 17:11:13 $
|
||||
|
||||
current maintainer: Peter Eisentraut <peter_e@gmx.net>
|
||||
Last updated: $Date: 2006/10/10 00:29:14 $
|
||||
|
||||
|
||||
Contents:
|
||||
@ -15,73 +13,89 @@ Contents:
|
||||
3) Why does configure complain about a failed test program?
|
||||
4) Why does my 64-bit build sometimes crash?
|
||||
5) How can I compile for optimum performance?
|
||||
6) How to compile PostgreSQL with Sun Studio?
|
||||
7) Where I can download prepared Solaris packages?
|
||||
8) How to tune PostgreSQL and Solaris for best performance?
|
||||
9) Can I use dtrace for tracing PostgreSQL?
|
||||
|
||||
1) What tools do I need to build and install PostgreSQL on Solaris?
|
||||
|
||||
You will need
|
||||
|
||||
- GNU zip (for installing the documentation)
|
||||
- GNU make
|
||||
- GNU readline library (optional)
|
||||
- GCC (if you don't have Sun's compiler)
|
||||
GNU zip (for installing the documentation)
|
||||
GNU make
|
||||
GNU readline library (optional)
|
||||
Sun Studio CC or GCC
|
||||
|
||||
If you like Solaris packages, you can find these tools here:
|
||||
http://www.sunfreeware.com
|
||||
You can download Sun Studio from:
|
||||
http://developers.sun.com/prodtech/cc/downloads/index.jsp
|
||||
|
||||
Many of GNU tools are integrated into the Solaris 10 or they are
|
||||
present on the Solaris companion CD.
|
||||
|
||||
If you like packages for older version of Solaris, you can find these
|
||||
tools here:
|
||||
|
||||
http://www.sunfreeware.com or http://www.blastwave.org
|
||||
|
||||
If you prefer sources, look here:
|
||||
http://www.gnu.org/order/ftp.html
|
||||
|
||||
You can build with either GCC or Sun's compiler suite. We have heard
|
||||
reports of problems when using gcc 2.95.1; gcc 2.95.3 or later is
|
||||
recommended. If you are using Sun's compiler, be careful *not* to
|
||||
select /usr/ucb/cc; use /opt/SUNWspro/bin/cc.
|
||||
http://www.gnu.org/order/ftp.html
|
||||
|
||||
You can build with either GCC or Sun's compiler suite. For better code
|
||||
optimalization Sun's compiler is strongly recommended on the SPARC
|
||||
architecture. We have heard reports of problems when using gcc 2.95.1;
|
||||
gcc 2.95.3 or later is recommended. If you are using Sun's compiler, be
|
||||
careful *not* to select /usr/ucb/cc; use /opt/SUNWspro/bin/cc.
|
||||
|
||||
|
||||
2) Why do I get problems when building with OpenSSL support?
|
||||
|
||||
When you build PostgreSQL with OpenSSL support you might get
|
||||
compilation errors in the following files:
|
||||
When you build PostgreSQL with OpenSSL support you might get compilation
|
||||
errors in the following files:
|
||||
|
||||
src/backend/libpq/crypt.c
|
||||
src/backend/libpq/password.c
|
||||
src/interfaces/libpq/fe-auth.c
|
||||
src/interfaces/libpq/fe-connect.c
|
||||
src/backend/libpq/crypt.c
|
||||
src/backend/libpq/password.c
|
||||
src/interfaces/libpq/fe-auth.c
|
||||
src/interfaces/libpq/fe-connect.c
|
||||
|
||||
This is because of a namespace conflict between the standard
|
||||
/usr/include/crypt.h header and the header files provided by OpenSSL.
|
||||
|
||||
Upgrading your OpenSSL installation to version 0.9.6a fixes this
|
||||
problem.
|
||||
problem. Solaris 9 and above already newer version of OpenSSL.
|
||||
|
||||
|
||||
3) Why does configure complain about a failed test program?
|
||||
|
||||
This is probably a case of the run-time linker being unable to find
|
||||
libz or some other non-standard library, such as libssl. To point it
|
||||
to the right location, set the LD_LIBRARY_PATH environment variable,
|
||||
e.g.,
|
||||
This is probably a case of the run-time linker being unable to find some
|
||||
library. On solaris 8 and older it should be libz or some other
|
||||
non-standard library, such as libssl. To point it to the right
|
||||
location, set the LD_LIBRARY_PATH environment variable, e.g.,
|
||||
|
||||
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/ssl/lib
|
||||
export LD_LIBRARY_PATH
|
||||
LD_LIBRARY_PATH=/usr/sfw/lib:/opt/sfw/lib:/usr/local/lib
|
||||
export LD_LIBRARY_PATH
|
||||
|
||||
and restart configure. You will also have to keep this setting
|
||||
whenever you run any of the installed PostgreSQL programs.
|
||||
|
||||
Alternatively, set the environment variable LD_RUN_PATH. See the
|
||||
ld(1) man page for more information.
|
||||
and restart configure. You will also have to keep this setting whenever
|
||||
you run any of the installed PostgreSQL programs. Alternatively, set
|
||||
the environment variable LD_RUN_PATH. See the ld(1) man page for more
|
||||
information.
|
||||
|
||||
|
||||
4) Why does my 64-bit build sometimes crash?
|
||||
|
||||
On Solaris 7 and older, the 64-bit version of libc has a buggy vsnprintf
|
||||
routine, which leads to erratic core dumps in PostgreSQL. The simplest known
|
||||
workaround is to force PostgreSQL to use its own version of vsnprintf rather
|
||||
than the library copy. To do this, after you run 'configure' edit a file
|
||||
produced by configure:
|
||||
routine, which leads to erratic core dumps in PostgreSQL. The simplest
|
||||
known workaround is to force PostgreSQL to use its own version of
|
||||
vsnprintf rather than the library copy. To do this, after you run
|
||||
'configure' edit a file produced by configure:
|
||||
|
||||
In src/Makefile.global, change the line
|
||||
|
||||
LIBOBJS =
|
||||
|
||||
to read
|
||||
|
||||
LIBOBJS = snprintf.o
|
||||
|
||||
(There might be other files already listed in this variable. Order
|
||||
@ -92,10 +106,78 @@ Then build as usual.
|
||||
|
||||
5) How can I compile for optimum performance?
|
||||
|
||||
Try using the "-fast" compile flag. The binaries might not be portable to
|
||||
other Solaris systems, and you might need to compile everything that links
|
||||
to PostgreSQL with "-fast", but PostgreSQL will run significantly faster,
|
||||
50% faster on some tests.
|
||||
On SPARC architecture Sun Studio is strongly recommended for
|
||||
compilation. Try using -xO5 optimalization flag to generate
|
||||
significantly faster binaries. Do not use any flags which modify
|
||||
behavior of floating point operations and errno processing (e.g.
|
||||
-fast). These flags should raise some nonstandard PostgreSQL behavior
|
||||
for example in the date/time computing.
|
||||
|
||||
If you do not reason to use 64-bit binaries on SPARC, prefer 32-bit
|
||||
version. The 64-bit operations are slower and 64-bit binaries are slower
|
||||
then 32-bits. And on other side a 32-bit code on the AMD64 CPU family is
|
||||
not native and that is why 32-bit code is significant slower on this
|
||||
CPU family.
|
||||
|
||||
|
||||
6) How to compile PostgreSQL with Sun Studio?
|
||||
|
||||
On Solaris 10 you can performed following steps:
|
||||
|
||||
export CC=/opt/SUNWspro/bin/cc
|
||||
export CFLAGS=-xO5
|
||||
export LDFLAGS=-lm
|
||||
./configure --without-readline
|
||||
gmake
|
||||
|
||||
|
||||
7) Where I can download prepared Solaris packages?
|
||||
|
||||
The PostgreSQL is bundled with Solaris 10 (from update 2). Official
|
||||
packages are too available on
|
||||
http://pgfoundry.org/projects/solarispackages/. Packages for older
|
||||
Solaris version (8,9) you can download from: http://www.sunfreeware.com
|
||||
or http://www.blastwave.org
|
||||
|
||||
|
||||
8) How to tune PostgreSQL and Solaris for best performance?
|
||||
|
||||
Some tuning tricks can be found here:
|
||||
|
||||
http://www.sun.com/servers/coolthreads/tnb/applications_postgresql.jsp
|
||||
|
||||
This article is primary focused on T2000 platform, however, many of
|
||||
recommendations are general for other hardware with Solaris.
|
||||
|
||||
|
||||
9) Can I use dtrace for tracing PostgreSQL?
|
||||
|
||||
The PostgreSQL 8.2 has implemented dtrace support. You can enable it by
|
||||
the --enable-dtrace configure switch. If you want to compile a 64-bit
|
||||
code with dtrace you must specify DTRACEFLAGS='-64', e.g.
|
||||
|
||||
Using gcc compiler:
|
||||
|
||||
$ ./configure CC='gcc -m64' --enable-dtrace DTRACEFLAGS='-64' ...
|
||||
|
||||
Using Sun compiler:
|
||||
|
||||
$ configure CC='/opt/SUNWspro/bin/cc -xtarget=native64' --enable-dtrace DTRACEFLAGS='-64'
|
||||
|
||||
|
||||
If you have some problem with postgres linking, looks like:
|
||||
|
||||
Undefined first referenced
|
||||
symbol in file
|
||||
AbortTransaction utils/probes.o
|
||||
CommitTransaction utils/probes.o
|
||||
ld: fatal: Symbol referencing errors. No output written to postgres
|
||||
collect2: ld returned 1 exit status
|
||||
gmake: *** [postgres] Error 1
|
||||
|
||||
check if you have Solaris 10u3 or newer installed on your box. You can
|
||||
also find more information here:
|
||||
|
||||
http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in
|
||||
|
||||
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
PostgreSQL(ポストグレス・キュー・エル)についてよくある質問とその解答(FAQ)
|
||||
|
||||
原文最終更新日: Sun Apr 2 23:40:12 EDT 2006
|
||||
原文最終更新日: Fri Aug 18 12:27:33 EDT 2006
|
||||
|
||||
現在の維持管理者: Bruce Momjian (pgman at candle.pha.pa.us)
|
||||
現在の維持管理者: Bruce Momjian (bruce@momjian.us)
|
||||
Maintainer of Japanese Translation: Jun Kuwamura (juk at PostgreSQL.jp)
|
||||
|
||||
この文書の最新版は http://www.postgresql.org/docs/faqs.FAQ.html で見ることがで
|
||||
@ -29,13 +29,13 @@ Maintainer of Japanese Translation: Jun Kuwamura (juk at PostgreSQL.jp)
|
||||
1.3) PostgreSQLの著作権はどうなってますか？
|
||||
1.4) PostgreSQLをサポートするプラットホームは？
|
||||
1.5) PostgreSQLはどこから入手できますか？
|
||||
1.6) 最新版はどれですか？
|
||||
1.6) 最新のリリースはどれですか？
|
||||
1.7) サポートはどこで受けられますか？
|
||||
1.8) バグレポートはどのように発信しますか？
|
||||
1.9) 既知のバグや未だ無い機能はどうやって見つけますか？
|
||||
1.10) どのような文書がありますか？
|
||||
1.11) SQLはどうすれば学べますか？
|
||||
1.12) 開発チームにはどのように参加しますか？
|
||||
1.12) パッチを提供したり、開発チーム参加するにはどうすればよいですか？
|
||||
1.13) 他のDBMSと比べてPostgreSQLはどうなのですか？
|
||||
|
||||
ユーザ・クライアントの質問
|
||||
@ -53,8 +53,7 @@ Maintainer of Japanese Translation: Jun Kuwamura (juk at PostgreSQL.jp)
|
||||
？
|
||||
3.4) どのようなデバグ機能が使えますか？
|
||||
3.5) 接続しようとするときに 'Sorry, too many clients' が出るのはなぜですか？
|
||||
3.6) PostgreSQLのメジャーリリースをアップデートするのにダンプとリストアをしなく
|
||||
てはならないのはなぜですか？
|
||||
3.6) PostgreSQLのアップグレードの手順はどうしますか？
|
||||
3.7) ハードウェアにはどんなコンピュータを使えばよいですか？
|
||||
|
||||
操作上の質問
|
||||
@ -199,7 +198,7 @@ SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
|
||||
す。リリースの時点で実際にテストを行なったことの報告がなされたプラットホームに
|
||||
ついてはインストール手引書に列挙してあります。
|
||||
|
||||
PostgreSQL は、Win2000, WinXP, そして、Win2003 のような Microsoft Windows NTベ
|
||||
PostgreSQL は、Win2000 SP4, WinXP, そして、Win2003 など Microsoft Windows NTベ
|
||||
ースのオペレーティングシステムで、ネイティブに走ります。あらかじめパッケージに
|
||||
されたインストーラが http://pgfoundry.org/projects/pginstaller にあり、利用でき
|
||||
ます。MSDOSベースのWindowsのバージョン(Win95, Win98, WinMe)では、Cygwinを使って
|
||||
@ -224,9 +223,9 @@ sh=1&button=Search&key=postgreSQL&stype=all&sort=type&dir=%2F
|
||||
Webブラウザ経由だと、 http://www.postgresql.org/ftp/、それから、ftp経由だと、
|
||||
ftp://ftp.PostgreSQL.org/pub/ を使います。
|
||||
|
||||
1.6) 最新版はどれですか？
|
||||
1.6) 最新のリリースはどれですか？
|
||||
|
||||
PostgreSQL の最新版はバージョン 8.1.3 です。
|
||||
PostgreSQL の最新版はバージョン 8.1.4 です。
|
||||
|
||||
我々は、1年毎にメジャーリリースを、数ヵ月ごとのマイナーリリースを行なうことを計
|
||||
画しています。
|
||||
@ -264,8 +263,8 @@ postgresql-es)
|
||||
]
|
||||
|
||||
|
||||
商用サポート会社のリストは http://techdocs.postgresql.org/companies.phpにありま
|
||||
す。
|
||||
商用サポート会社のリストは http://www.postgresql.org/support/
|
||||
professional_supportにあります。
|
||||
|
||||
1.8) バグレポートはどのように発信しますか？
|
||||
|
||||
@ -359,9 +358,12 @@ The Practical SQL Handbook, Bowman Judith S. et al., Addison-Wesley
|
||||
ーザに好評です。ほかでは、The Complete Reference SQL, Groff et al., McGraw-Hill
|
||||
も好評です。
|
||||
|
||||
素晴らしい手引書は、http://www.intermedia.net/support/sql/sqltut.shtm, http://
|
||||
ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM, そして、http://
|
||||
sqlcourse.com にあります。
|
||||
素晴らしい手引書は、
|
||||
|
||||
http://www.intermedia.net/support/sql/sqltut.shtm
|
||||
http://sqlcourse.com
|
||||
http://www.w3schools.com/sql/default.asp
|
||||
http://mysite.verizon.net/Graeme_Birchall/id1.html にあります。
|
||||
|
||||
[訳注:
|
||||
日本PostgreSQLユーザ会の日本語の参考文献の紹介ページ
|
||||
@ -382,7 +384,7 @@ http://www.postgresql.jp/PostgreSQL/references.html
|
||||
]
|
||||
|
||||
|
||||
1.12) 開発チームにはどのように参加しますか？
|
||||
1.12) パッチを提供したり、開発チーム参加するにはどうすればよいですか？
|
||||
|
||||
（開発者向けの）Developer's FAQをごらんください。
|
||||
|
||||
@ -459,8 +461,8 @@ Web
|
||||
|
||||
2.3) PostgreSQL にグラフィカル・ユーザインターフェースはありますか？
|
||||
|
||||
もちろん、あります。詳細は、http://techdocs.postgresql.org/guides/GUITools をご
|
||||
らんください。
|
||||
商用とオープンソース開発者によるもの両方で、PostgreSQLには多くのGUIツールが利用
|
||||
可能で、詳細なリストは、PostgreSQLコミュニティ文書でごらんください。
|
||||
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
@ -506,9 +508,9 @@ Web
|
||||
んください。
|
||||
|
||||
ハードウェアの選定
|
||||
性能におけるハードウェアの影響は http://candle.pha.pa.us/main/writings/
|
||||
pgsql/hw_performance/index.html (JPUGサイトの日本語版) と http://
|
||||
www.powerpostgresql.com/PerfList/ に述べられています。
|
||||
性能におけるハードウェアの影響は http://www.powerpostgresql.com/PerfList/
|
||||
と、 http://momjian.us/main/writings/pgsql/hw_performance/index.html (JPUG
|
||||
サイトの日本語版) に述べられています。
|
||||
|
||||
|
||||
[訳注:
|
||||
@ -530,16 +532,23 @@ postmaster
|
||||
postgresql.conf の中の max_connections の値を変更して postmasterを再起動するこ
|
||||
とで可能になります。
|
||||
|
||||
3.6) PostgreSQLのメジャーリリースをアップデートするのにダンプとリストアをしなく
|
||||
てはならないのはなぜですか？
|
||||
3.6) PostgreSQLのアップグレードの手順はどうしますか？
|
||||
|
||||
PostgreSQLチームはマイナーリリースでは小さな変更しか行ないませんので、7.4.0 か
|
||||
ら 7.4.1 へのアップグレードにはダンプとリストアの必要はありません。しかし、メジ
|
||||
ャーリリース(たとえば、7.2から7.3へのような) では、システムテーブルやデータファ
|
||||
イルの内部フォーマットの変更をしばしば行ないます。これらの変更はたいてい複雑で
|
||||
、そのため我々はデータファイルのための後方互換性を維持することができません。ダ
|
||||
ンプは汎用フォーマットでデータを出力し、それを新しい内部フォーマットに読み込む
|
||||
ことができます。
|
||||
PostgreSQLチームはマイナーリリースではバグの修正しか行ないませんので、たとえば
|
||||
7.4.8 から 7.4.9 へのアップグレードにダンプとリストアは必要ありません。したがっ
|
||||
て、データベースサーバを一時的に停止して、アップデートしたバイナリをインストー
|
||||
ルし、そして、サーバをリスタートするだけです。
|
||||
|
||||
全ユーザはできるだけ早く最新のマイナーリリースにアップグレードするべきです。す
|
||||
べてのアップグレードにリスクはつきものですが、 PostgreSQLのマイナーリリースは、
|
||||
なるべく小さなリスクで一般的なバグの修正だけを目論んだものです。我々コミュニテ
|
||||
ィの中ではアップグレードしないほうがもっとリスクが高いものと考えられています。
|
||||
|
||||
しかし、メジャーリリース（たとえば、7.3 から 7.4 のような）では、システムテーブ
|
||||
ルやデータファイルの内部フォーマットの変更をしばしば行ないます。これらの変更は
|
||||
たいてい複雑で、そのため我々はデータファイルのための後方互換性を維持することが
|
||||
できません。メジャーアップグレードのためには、データベースのダンプ/リロードが必
|
||||
要です。
|
||||
|
||||
3.7) ハードウェアにはどんなコンピュータを使えばよいですか？
|
||||
|
||||
@ -627,7 +636,8 @@ VACUUM FULL tab
|
||||
ファイルシステムの制限は重要ではありません。
|
||||
|
||||
デフォルトのブロックサイズを32kに増加することで、最大テーブルサイズと行サイズと
|
||||
最大カラム数とを4倍にすることができます。
|
||||
最大カラム数とを4倍にすることができます。また、最大テーブルサイズはテーブルパー
|
||||
ティションを使って増やすこともできます。
|
||||
|
||||
ひとつの制限は、約2,000文字以上の長さのカラムにインデックスを付けることができな
|
||||
いことです。幸いにも、そのようなインデックスは実際は必要ありません。長いカラム
|
||||
@ -998,7 +1008,7 @@ client_encoding
|
||||
[訳注：
|
||||
日本語版の製作については以下の通りです。
|
||||
|
||||
最終更新日: 2006年04月03日
|
||||
最終更新日: 2006年08月19日
|
||||
翻訳者: 桑村 潤 (Jun Kuwamura <juk at PostgreSQL.jp>)
|
||||
|
||||
このFAQの和訳の作成にあたり協力をしてくださった方々(敬称は略させていただきます):
|
||||
@ -1007,7 +1017,7 @@ client_encoding
|
||||
石井 達夫(Tatsuo ISHII <t-ishii at sra.co.jp>)
|
||||
齊藤 知人(Tomohito SAITOH <tomos at elelab.nsc.co.jp>)
|
||||
馬場 肇(Hajime BABA <baba at kusastro.kyoto-u.ac.jp>)
|
||||
岡本 一幸(Kazuyuki OKAMOTO <kokamoto at itg.hitachi.co.jp>)
|
||||
岡本 一幸(Kazuyuki OKAMOTO <kaz-okamoto at hitachi-system.co.jp>)
|
||||
小菅 昭一(Shoichi Kosuge <s-kosuge at str.hitachi.co.jp>)
|
||||
山下 義之(Yoshiyuki YAMASHITA <dica at eurus.dti.ne.jp>)
|
||||
境 真太郎(Sintaro SAKAI <s_sakai at mxn.mesh.ne.jp>)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
|
||||
Otvety na chasto zadavaemye voprosy po PostgreSQL
|
||||
|
||||
Data poslednego obnovleniya: Pyatnica 24 fevralya 23:28:40 EDT 2006
|
||||
Data poslednego obnovleniya: Voskresen'e 18 iyunya 15:33:25 EDT 2006
|
||||
|
||||
Anglijskij variant soprovozhdaet: Bryus Mom'yan (Bruce Momjian)
|
||||
(pgman@candle.pha.pa.us)
|
||||
@ -22,14 +22,15 @@
|
||||
1.3) Kakovy avtorskie prava na PostgreSQL?
|
||||
1.4) Na kakih platformah rabotaet PostgreSQL?
|
||||
1.5) Gde mozhno vzyat' PostgreSQL?
|
||||
1.6) Kakaya versiya poslednyaya?
|
||||
1.6) Kakaya versiya naibolee svezhaya?
|
||||
1.7) Gde poluchit' podderzhku?
|
||||
1.8) Kak mne soobschit' ob oshibke?
|
||||
1.9) Kak najti informaciyu ob izvestnyh oshibkah ili otsutstvuyuschih
|
||||
vozmozhnostyah?
|
||||
1.10) Kakaya dokumentaciya imeetsya v nalichii?
|
||||
1.11) Kak nauchit'sya SQL?
|
||||
1.12) Kak prisoedinitsya k komande razrabotchikov?
|
||||
1.12) Kak mne otpravit' ispravlenie ili prisoedinitsya k komande
|
||||
razrabotchikov?
|
||||
1.13) Kak sravnit' PostgreSQL s drugimi SUBD?
|
||||
|
||||
Voprosy pol'zovatelej po klientskoj chasti
|
||||
@ -49,8 +50,7 @@
|
||||
3.4) Kakie vozmozhnosti dlya otladki est' v nalichii?
|
||||
3.5) Pochemu ya poluchayu soobschenie "Sorry, too many clients" kogda
|
||||
pytayus' podklyuchit'sya k baze?
|
||||
3.6) Pochemu neobhodimo delat' dump i restore pri obnovlenii vypuskov
|
||||
PostgreSQL?
|
||||
3.6) Kak vypolnit' obnovlenie PostgreSQL?
|
||||
3.7) Kakoe komp'yuternoe "zhelezo" ya dolzhen ispol'zovat'?
|
||||
|
||||
Voprosy `ekspluatacii
|
||||
@ -189,9 +189,9 @@
|
||||
CHerez brauzer, ispol'zuya http://www.postgresql.org/ftp/ i cherez
|
||||
ftp, ispol'zuya ftp://ftp.PostgreSQL.org/pub/.
|
||||
|
||||
1.6) Kakaya poslednyaya versiya?
|
||||
1.6) Kakaya versiya naibolee svezhaya?
|
||||
|
||||
Poslednij vypusk PostgreSQL - `eto versiya 8.1.3
|
||||
Poslednij vypusk PostgreSQL - `eto versiya 8.1.4
|
||||
|
||||
My planiruem vypuskat' novye starshie versii kazhdyj god, a mladshie
|
||||
versii kazhdye neskol'ko mesyacev.
|
||||
@ -304,12 +304,16 @@
|
||||
iz nashih pol'zovatelej nravitsya kniga The Practical SQL Handbook,
|
||||
Bowman, Judith S., et al., Addison-Wesley. Drugim nravitsya The
|
||||
Complete Reference SQL, Groff et al., McGraw-Hill.
|
||||
Est' prekrasnyj uchebnik na
|
||||
http://www.intermedia.net/support/sql/sqltut.shtm, na
|
||||
http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,
|
||||
i na http://sqlcourse.com.
|
||||
|
||||
1.12) Kak prisoedinitsya k komande razrabotchikov?
|
||||
Suschestvuet takzhe mnozhestvo prekrasnyh uchebnikov dostupnyh v
|
||||
online:
|
||||
* http://www.intermedia.net/support/sql/sqltut.shtm,
|
||||
* http://sqlcourse.com.
|
||||
* http://www.w3school.com/sql/default.asp
|
||||
* http://mysite.verizon.net/Graeme_Birchall/id1.html
|
||||
|
||||
1.12) Kak mne prislat' ispravlenie ili prisoedinitsya k komande
|
||||
razrabotchikov?
|
||||
|
||||
Smotrite FAQ dlya razrabotchikov.
|
||||
|
||||
@ -394,8 +398,9 @@
|
||||
|
||||
2.3) Est' li u PostgreSQL graficheskij interfejs pol'zovatelya?
|
||||
|
||||
Da, podrobnosti smotrite v
|
||||
http://techdocs.postgresql.org/guides/GUITools.
|
||||
Dlya PostgreSQL suschestvuet bol'shoe kolichestvo instrumentov s
|
||||
graficheskim interfejsom kak kommercheskih, tak i otkrytyh.
|
||||
Podrobnosti mozhno najti v Dokumentacii soobschestva PostgreSQL
|
||||
_________________________________________________________________
|
||||
|
||||
Voprosy administrirovaniya
|
||||
@ -466,23 +471,26 @@
|
||||
izmeniv znachenie max_connections v fajle postgresql.conf i
|
||||
perestartovat' postmaster.
|
||||
|
||||
3.6) Pochemu neobhodimo delat' dump i restore pri obnovlenii vypuskov
|
||||
PostgreSQL?
|
||||
3.6) Kak vypolnit' obnovlenie PostgreSQL?
|
||||
|
||||
Razrabotchiki PostgreSQL delayut tol'ko nebol'shie izmeneniya mezhdu
|
||||
podvypuskami. Takim obrazom obnovlenie s versii 7.4.0 do 7.4.1 ne
|
||||
trebuet vypolneniya dump i restore. Odnako pri vyhode ocherednogo
|
||||
vypuska (t.e. pri obnovlenii naprimer, s 7.3 na 7.4) chasto menyaetsya
|
||||
vnutrennij format sistemnyh tablic i fajlov dannyh. `Eti izmeneniya
|
||||
chasto nosyat kompleksnyj harakter, tak chto net vozmozhnosti
|
||||
obespechit' obratnuyu sovmestimost' fajlov dannyh. Vypolenie dump
|
||||
pozvolyaet poluchit' dannye v obschem formate, kotoryj zatem mozhet
|
||||
byt' zagruzhen pri ispol'zovanii novogo vnutrennego formata.
|
||||
Mezhdu podvypuskami, razrabotchiki PostgreSQL delayut tol'ko
|
||||
ispravleniya oshibok. Takim obrazom obnovlenie s versii 7.4.8 do 7.4.9
|
||||
ne trebuet vypolneniya dump i restore; dostatochno ostanovit' server,
|
||||
ustanovit' obnovlionnye fajly SUBD i zapustit' server.
|
||||
|
||||
V teh vypuskah, gde format dannyh na diske ne menyaetsya, dlya
|
||||
provedeniya obnovleniya mozhet byt' ispol'zovan scenarij pg_upgrade
|
||||
bez ispol'zovaniya dump/restore. Kommentarii k vypusku govorit kogda
|
||||
mozhno ispol'zovat' pg_upgrade dlya `etogo vypuska.
|
||||
Vse pol'zovateli dolzhny by obnovlyat'sya na naibolee svezhuyu
|
||||
podversiyu kak tol'ko ona budet dostupna. V to vremya kak kazhdoe
|
||||
obnovlenie podrazumevaet nekotoryj risk, podversii PostgreSQL
|
||||
razrabytyvayutsya tol'ko dlya ispravleniya obschih oshibok s
|
||||
minimal'nym riskom. Takim obrazom, vash risk svyazan tol'ko s samim
|
||||
obnovleniem.
|
||||
|
||||
Pri vyhode ocherednogo vypuska (t.e. pri obnovlenii naprimer, s 7.3 na
|
||||
7.4) chasto menyaetsya vnutrennij format sistemnyh tablic i fajlov
|
||||
dannyh. `Eti izmeneniya chasto nosyat slozhnyj harakter, tak chto my
|
||||
ne obsluzhivaem obratnuyu sovmestimost' dlya fajlov dannyh. V `etih
|
||||
sluchayah dlya obnovleniya bazy dannyh trebuetsya vypolnit'
|
||||
dump/restore.
|
||||
|
||||
3.7) Kakoe komp'yuternoe "zhelezo" ya dolzhen ispol'zovat'?
|
||||
|
||||
@ -556,7 +564,7 @@
|
||||
|
||||
Maksimal'nyj razmer bazy? neogranichen (suschestvuyut bazy na 32 TB)
|
||||
Maksimal'nyj razmer tablicy? 32 TB
|
||||
Maksimal'nyj razmer stroki? 1.6 TB
|
||||
Maksimal'nyj razmer stroki? 400 Gb
|
||||
Maksimal'nyj razmer polya? 1 GB
|
||||
Maksimal'noe kolichestvo strok v tablice? neogranicheno
|
||||
Maksimal'noe kolichestvo kolonok v tablice? 250-1600 v zavisimosti ot
|
||||
|
||||
@ -10,10 +10,10 @@
|
||||
alink="#0000ff">
|
||||
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
|
||||
|
||||
<P>Last updated: Thu May 18 23:52:32 EDT 2006</P>
|
||||
<P>Last updated: Mon Oct 9 20:28:14 EDT 2006</P>
|
||||
|
||||
<P>Current maintainer: Bruce Momjian (<A href=
|
||||
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
|
||||
"mailto:bruce@momjian.us">bruce@momjian.us</A>)
|
||||
</P>
|
||||
|
||||
<P>The most recent version of this document can be viewed at <A href=
|
||||
@ -31,7 +31,7 @@
|
||||
<A href="#item1.3">1.3</A>) What is the copyright of PostgreSQL?<BR>
|
||||
<A href="#item1.4">1.4</A>) What platforms does PostgreSQL support?<BR>
|
||||
<A href="#item1.5">1.5</A>) Where can I get PostgreSQL?<BR>
|
||||
<A href="#item1.6">1.6</A>) What is the latest release?<BR>
|
||||
<A href="#item1.6">1.6</A>) What is the most recent release?<BR>
|
||||
<A href="#item1.7">1.7</A>) Where can I get support?<BR>
|
||||
<A href="#item1.8">1.8</A>) How do I submit a bug report?<BR>
|
||||
<A href="#item1.9">1.9</A>) How do I find out about known bugs or
|
||||
@ -63,8 +63,7 @@
|
||||
<A href="#item3.4">3.4</A>) What debugging features are available?<BR>
|
||||
<A href="#item3.5">3.5</A>) Why do I get <I>"Sorry, too many
|
||||
clients"</I> when trying to connect?<BR>
|
||||
<A href="#item3.6">3.6</A>) Why do I need to do a dump and restore
|
||||
to upgrade PostgreSQL releases?<BR>
|
||||
<A href="#item3.6">3.6</A> What is the upgrade process for PostgreSQL?<BR>
|
||||
<A href="#item3.7">3.7</A>) What computer hardware should I use?<BR>
|
||||
|
||||
|
||||
@ -200,7 +199,7 @@
|
||||
instructions.</P>
|
||||
|
||||
<P>PostgreSQL also runs natively on Microsoft Windows NT-based operating
|
||||
systems like Win2000, WinXP, and Win2003. A prepackaged installer is
|
||||
systems like Win2000 SP4, WinXP, and Win2003. A prepackaged installer is
|
||||
available at <a href= "http://pgfoundry.org/projects/pginstaller">
|
||||
http://pgfoundry.org/projects/pginstaller</a>. MSDOS-based versions
|
||||
of Windows (Win95, Win98, WinMe) can run PostgreSQL using Cygwin.</P>
|
||||
@ -218,7 +217,7 @@
|
||||
<A href="ftp://ftp.PostgreSQL.org/pub/">
|
||||
ftp://ftp.PostgreSQL.org/pub/</A>.</P>
|
||||
|
||||
<H3 id="item1.6">1.6) What is the latest release?</H3>
|
||||
<H3 id="item1.6">1.6) What is the most recent release?</H3>
|
||||
|
||||
<P>The latest release of PostgreSQL is version 8.1.5.</P>
|
||||
|
||||
@ -241,8 +240,8 @@
|
||||
(<I>#postgresqlfr</I>). There is also a PostgreSQL channel on EFNet.</P>
|
||||
|
||||
<P>A list of commercial support companies is available at <A href=
|
||||
"http://techdocs.postgresql.org/companies.php">
|
||||
http://techdocs.postgresql.org/companies.php</A>.</P>
|
||||
"http://www.postgresql.org/support/professional_support">
|
||||
http://www.postgresql.org/support/professional_support</A>.</P>
|
||||
|
||||
<H3 id="item1.8">1.8) How do I submit a bug report?</H3>
|
||||
|
||||
@ -472,9 +471,10 @@
|
||||
<H3 id="item2.3">2.3) Does PostgreSQL have a graphical user
|
||||
interface?</H3>
|
||||
|
||||
<P>Yes, see <a href="http://techdocs.postgresql.org/guides/GUITools">
|
||||
http://techdocs.postgresql.org/guides/GUITools</a> for a
|
||||
detailed list.</P>
|
||||
<P>There are a large number of GUI Tools that are available for PostgreSQL
|
||||
from both commercial and open source developers. A detailed list can be
|
||||
found in the <A href="http://www.postgresql.org/docs/techdocs.54">
|
||||
PostgreSQL Community Documentation</A></P>
|
||||
|
||||
<HR>
|
||||
|
||||
@ -544,11 +544,11 @@
|
||||
|
||||
<DT><B>Hardware Selection</B></DT>
|
||||
|
||||
<DD>The effect of hardware on performance is detailed in <a
|
||||
href="http://candle.pha.pa.us/main/writings/pgsql/hw_performance/index.html">
|
||||
http://candle.pha.pa.us/main/writings/pgsql/hw_performance/index.html</a> and
|
||||
<DD>The effect of hardware on performance is detailed in
|
||||
<a href="http://www.powerpostgresql.com/PerfList/">
|
||||
http://www.powerpostgresql.com/PerfList/</a>.
|
||||
http://www.powerpostgresql.com/PerfList/</a> and <a
|
||||
href="http://momjian.us/main/writings/pgsql/hw_performance/index.html">
|
||||
http://momjian.us/main/writings/pgsql/hw_performance/index.html</a>.
|
||||
<BR>
|
||||
<BR>
|
||||
</DD>
|
||||
@ -570,16 +570,23 @@
|
||||
<I>max_connections</I> value in <I>postgresql.conf</I> and
|
||||
restarting the <I>postmaster</I>.</P>
|
||||
|
||||
<H3 id="item3.6">3.6) Why do I need to do a dump and restore
|
||||
to upgrade between major PostgreSQL releases?</H3>
|
||||
<H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3>
|
||||
|
||||
<P>The PostgreSQL team makes only small changes between minor releases,
|
||||
so upgrading from 7.4.0 to 7.4.1 does not require a dump and restore.
|
||||
However, major releases (e.g. from 7.3 to 7.4) often change the internal
|
||||
<P>The PostgreSQL team makes only bug fixes in minor releases,
|
||||
so, for example, upgrading from 7.4.8 to 7.4.9 does not require
|
||||
a dump and restore; merely stop the database server, install
|
||||
the updated binaries, and restart the server.</P>
|
||||
|
||||
<P>All users should upgrade to the most recent minor release as
|
||||
soon as it is available. While every upgrade has some risk,
|
||||
PostgreSQL minor releases are designed to fix only common bugs
|
||||
with the least risk. The community considers <i>not</i> upgrading
|
||||
more risky that upgrading.</P>
|
||||
|
||||
<P>Major releases (e.g. from 7.3 to 7.4) often change the internal
|
||||
format of system tables and data files. These changes are often complex,
|
||||
so we don't maintain backward compatibility for data files. A dump outputs
|
||||
data in a generic format that can then be loaded in using the new internal
|
||||
format.</P>
|
||||
so we don't maintain backward compatibility for data files. A dump/reload
|
||||
of the database is required for major upgrades.</P>
|
||||
|
||||
<H3 id="item3.7">3.7) What computer hardware should I use?</H3>
|
||||
|
||||
@ -687,7 +694,7 @@ table?</TD><TD>unlimited</TD></TR>
|
||||
|
||||
<P>One limitation is that indexes can not be created on columns
|
||||
longer than about 2,000 characters. Fortunately, such indexes are
|
||||
rarely needed. Uniqueness is best guaranteed by a funtion index
|
||||
rarely needed. Uniqueness is best guaranteed by a function index
|
||||
of an MD5 hash of the long column, and full text indexing
|
||||
allows for searching of words within the column.</P>
|
||||
|
||||
@ -805,8 +812,8 @@ table?</TD><TD>unlimited</TD></TR>
|
||||
FROM tab
|
||||
WHERE lower(col) = 'abc';
|
||||
</PRE>
|
||||
This will not use an standard index. However, if you create a
|
||||
expresssion index, it will be used:
|
||||
This will not use an standard index. However, if you create an
|
||||
expression index, it will be used:
|
||||
<PRE>
|
||||
CREATE INDEX tabindex ON tab (lower(col));
|
||||
</PRE>
|
||||
@ -950,7 +957,7 @@ length</TD></TR>
|
||||
|
||||
<P>Every row that is created in PostgreSQL gets a unique
|
||||
<SMALL>OID</SMALL> unless created <SMALL>WITHOUT OIDS</SMALL>.
|
||||
O<SMALL>ID</SMALL>s are autotomatically assigned unique 4-byte
|
||||
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. PostgreSQL uses <SMALL>OID</SMALL>s to link its
|
||||
|
||||
@ -13,10 +13,10 @@
|
||||
<H1>Developer's Frequently Asked Questions (FAQ) for
|
||||
PostgreSQL</H1>
|
||||
|
||||
<P>Last updated: Wed Mar 1 17:24:48 EST 2006</P>
|
||||
<P>Last updated: Wed Sep 6 20:12:13 EDT 2006</P>
|
||||
|
||||
<P>Current maintainer: Bruce Momjian (<A href=
|
||||
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
|
||||
"mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
|
||||
</P>
|
||||
|
||||
<P>The most recent version of this document can be viewed at <A
|
||||
@ -177,7 +177,7 @@
|
||||
<li>The patch should be generated in contextual diff format (<i>diff
|
||||
-c</i> and should be applicable from the root directory. If you are
|
||||
unfamiliar with this, you might find the script
|
||||
<I>src/tools/makediff/difforig</I> useful. (Unified diffs are only
|
||||
<I>src/tools/make_diff/difforig</I> useful. (Unified diffs are only
|
||||
preferable if the file changes are single-line changes and do not
|
||||
rely on surrounding lines.)</li>
|
||||
|
||||
@ -199,7 +199,7 @@
|
||||
"#1.16">1.16</a>.</li>
|
||||
|
||||
<li>If you are adding a new feature, confirm that it has been tested
|
||||
thoughly. Try to test the feature in all conceivable
|
||||
thoroughly. Try to test the feature in all conceivable
|
||||
scenarios.</li>
|
||||
|
||||
<li>If it is a performance patch, please provide confirming test
|
||||
@ -222,7 +222,9 @@
|
||||
<P>Other than documentation in the source tree itself, you can find
|
||||
some papers/presentations discussing the code at <A href=
|
||||
"http://www.postgresql.org/developer">
|
||||
http://www.postgresql.org/developer</A>.</P>
|
||||
http://www.postgresql.org/developer</A>. An excellent presentation
|
||||
is at <a href=
|
||||
"http://neilconway.org/talks/hacking/">http://neilconway.org/talks/hacking/</a></P>
|
||||
|
||||
<H3 id="item1.7">1.7) How do I download/update the current
|
||||
source tree?</H3>
|
||||
@ -355,9 +357,9 @@
|
||||
can be applied to the distribution. This produces context diffs,
|
||||
which is our preferred format.</P>
|
||||
|
||||
<P>Our standard format is to indent each code level with one tab,
|
||||
where each tab is four spaces. You will need to set your editor to
|
||||
display tabs as four spaces:<BR>
|
||||
<P>Our standard format <I>BSD</I> style, with each level of code indented
|
||||
one tab, where each tab is four spaces. You will need to set your editor
|
||||
or file viewer to display tabs as four spaces:<BR>
|
||||
</P>
|
||||
<PRE>
|
||||
vi in ~/.exrc:
|
||||
@ -367,45 +369,16 @@
|
||||
more -x4
|
||||
less:
|
||||
less -x4
|
||||
emacs:
|
||||
M-x set-variable tab-width
|
||||
|
||||
or
|
||||
|
||||
(c-add-style "pgsql"
|
||||
'("bsd"
|
||||
(indent-tabs-mode . t)
|
||||
(c-basic-offset . 4)
|
||||
(tab-width . 4)
|
||||
(c-offsets-alist .
|
||||
((case-label . +)))
|
||||
)
|
||||
nil ) ; t = set this style, nil = don't
|
||||
|
||||
(defun pgsql-c-mode ()
|
||||
(c-mode)
|
||||
(c-set-style "pgsql")
|
||||
)
|
||||
|
||||
and add this to your autoload list (modify file path in macro):
|
||||
|
||||
(setq auto-mode-alist
|
||||
(cons '("\\`/home/andrew/pgsql/.*\\.[chyl]\\'" . pgsql-c-mode)
|
||||
auto-mode-alist))
|
||||
or
|
||||
/*
|
||||
* Local variables:
|
||||
* tab-width: 4
|
||||
* c-indent-level: 4
|
||||
* c-basic-offset: 4
|
||||
* End:
|
||||
*/
|
||||
</PRE>
|
||||
<BR>
|
||||
<I>pgindent</I> will the format code by specifying flags to your
|
||||
<P>The <I>tools/editors</I> directory of the latest sources contains sample
|
||||
settings that can be used with the <I>emacs</I>, <I>xemacs</I> and
|
||||
<I>vim</I> editors, that assist in keeping to PostgreSQL coding standards.
|
||||
</P>
|
||||
|
||||
<P><I>pgindent</I> will the format code by specifying flags to your
|
||||
operating system's utility <I>indent.</I> This <A href=
|
||||
"http://ezine.daemonnews.org/200112/single_coding_style.html">article</A>
|
||||
describes the value of a consistent coding style.
|
||||
describes the value of a consistent coding style.</P>
|
||||
|
||||
<P><I>pgindent</I> is run on all source files just before each beta
|
||||
test period. It auto-formats all source files to make them
|
||||
@ -704,7 +677,7 @@
|
||||
http://www.cse.iitb.ac.in/dbms/Data/Papers-Other/SQL1999/ansi-iso-9075-2-1999.pdf</A></LI>
|
||||
|
||||
<LI>SQL:2003 <A href=
|
||||
"http://www.wiscorp.com/sql/sql_2003_standard.zip">http://www.wiscorp.com/sql/sql_2003_standard.zip</A></LI>
|
||||
"http://www.wiscorp.com/sql_2003_standard.zip">http://www.wiscorp.com/sql_2003_standard.zip</A></LI>
|
||||
</UL>
|
||||
|
||||
<P>Some SQL standards web pages are:</P>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -9,9 +9,9 @@
|
||||
<div id="pgContentWrap">
|
||||
|
||||
<h1>PostgreSQL(ポストグレス・キュー・エル)についてよくある質問とその解答(FAQ)</h1>
|
||||
<p>原文最終更新日: Sun Apr 2 23:40:12 EDT 2006</p>
|
||||
<p>原文最終更新日: Fri Aug 18 12:27:33 EDT 2006</p>
|
||||
<p>現在の維持管理者: Bruce Momjian (<A
|
||||
href="mailto:pgman at candle.pha.pa.us">pgman at candle.pha.pa.us</a>)<br />
|
||||
href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br />
|
||||
Maintainer of Japanese Translation: Jun Kuwamura (<A
|
||||
href="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp</a>)<br /></p>
|
||||
<p>この文書の最新版は<a href=
|
||||
@ -45,13 +45,13 @@ href="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp</a>)<br /></p>
|
||||
<a href="#item1.3">1.3</a>) PostgreSQLの著作権はどうなってますか？<br />
|
||||
<a href="#item1.4">1.4</a>) PostgreSQLをサポートするプラットホームは？<br />
|
||||
<a href="#item1.5">1.5</a>) PostgreSQLはどこから入手できますか？<br />
|
||||
<a href="#item1.6">1.6</a>) 最新版はどれですか？<br />
|
||||
<a href="#item1.6">1.6</a>) 最新のリリースはどれですか？<br />
|
||||
<a href="#item1.7">1.7</a>) サポートはどこで受けられますか？<br />
|
||||
<a href="#item1.8">1.8</a>) バグレポートはどのように発信しますか？<br />
|
||||
<a href="#item1.9">1.9</a>) 既知のバグや未だ無い機能はどうやって見つけますか？<br />
|
||||
<a href="#item1.10">1.10</a>) どのような文書がありますか？<br />
|
||||
<a href="#item1.11">1.11</a>) <small>SQL</small>はどうすれば学べますか？<br />
|
||||
<a href="#item1.12">1.12</a>) 開発チームにはどのように参加しますか？<br />
|
||||
<a href="#item1.12">1.12</a>) パッチを提供したり、開発チーム参加するにはどうすればよいですか？<br />
|
||||
<a href="#item1.13">1.13</a>) 他の<small>DBMS</small>と比べてPostgreSQLはどうなのですか？<br />
|
||||
|
||||
|
||||
@ -69,7 +69,7 @@ href="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp</a>)<br /></p>
|
||||
<a href="#item3.3">3.3</a>) より良い性能を得るためには、データベース・エンジンをどのように調整しますか？<br />
|
||||
<a href="#item3.4">3.4</a>) どのようなデバグ機能が使えますか？<br />
|
||||
<a href="#item3.5">3.5</a>) 接続しようとするときに <i>'Sorry, too many clients'</i> が出るのはなぜですか？<br />
|
||||
<a href="#item3.6">3.6</a>) PostgreSQLのメジャーリリースをアップデートするのにダンプとリストアをしなくてはならないのはなぜですか？<br />
|
||||
<a href="#item3.6">3.6</a>) PostgreSQLのアップグレードの手順はどうしますか？<br />
|
||||
<a href="#item3.7">3.7</a>) ハードウェアにはどんなコンピュータを使えばよいですか？<br />
|
||||
|
||||
|
||||
@ -221,7 +221,7 @@ href="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp</a>)<br /></p>
|
||||
なされたプラットホームについてはインストール手引書に列挙してあります。
|
||||
</p>
|
||||
|
||||
<p>PostgreSQL は、Win2000, WinXP, そして、Win2003 のような Microsoft
|
||||
<p>PostgreSQL は、Win2000 SP4, WinXP, そして、Win2003 など Microsoft
|
||||
Windows NTベースのオペレーティングシステムで、ネイティブに走ります。
|
||||
あらかじめパッケージにされたインストーラが<a href=
|
||||
"http://pgfoundry.org/projects/pginstaller">
|
||||
@ -255,9 +255,9 @@ href="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp</a>)<br /></p>
|
||||
ftp://ftp.PostgreSQL.org/pub/</a> を使います。</p>
|
||||
|
||||
|
||||
<h4 id="item1.6">1.6</a>) 最新版はどれですか？</h4>
|
||||
<h4 id="item1.6">1.6</a>) 最新のリリースはどれですか？</h4>
|
||||
|
||||
<p>PostgreSQL の最新版はバージョン 8.1.3 です。</p>
|
||||
<p>PostgreSQL の最新版はバージョン 8.1.4 です。</p>
|
||||
<p>我々は、1年毎にメジャーリリースを、数ヵ月ごとのマイナーリリースを
|
||||
行なうことを計画しています。</p>
|
||||
|
||||
@ -304,8 +304,8 @@ href="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp</a>)<br /></p>
|
||||
</pre></small></p>
|
||||
|
||||
<p>商用サポート会社のリストは<a
|
||||
href="http://techdocs.postgresql.org/companies.php">
|
||||
http://techdocs.postgresql.org/companies.php</a>にあります。</p>
|
||||
href="http://www.postgresql.org/support/professional_support">
|
||||
http://www.postgresql.org/support/professional_support</a>にあります。</p>
|
||||
|
||||
|
||||
<h4 id="item1.8">1.8</a>) バグレポートはどのように発信しますか？
|
||||
@ -442,11 +442,20 @@ href="mailto:juk at PostgreSQL.jp">juk at PostgreSQL.jp</a>)<br /></p>
|
||||
|
||||
|
||||
<p>素晴らしい手引書は、<a href=
|
||||
"http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</a>
|
||||
<a href=
|
||||
"http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
|
||||
http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,</a>
|
||||
そして、<a href="http://sqlcourse.com/">http://sqlcourse.com</a>
|
||||
<ul>
|
||||
<li> <a href="http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://sqlcourse.com/">http://sqlcourse.com</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.w3schools.com/sql/default.asp">http://www.w3schools.com/sql/default.asp</a>
|
||||
</li>
|
||||
<li><a href=
|
||||
"http://mysite.verizon.net/Graeme_Birchall/id1.html">http://mysite.verizon.net/Graeme_Birchall/id1.html</a>
|
||||
</li>
|
||||
</ul>
|
||||
にあります。</p>
|
||||
|
||||
|
||||
@ -470,7 +479,7 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
]
|
||||
</pre></small></p>
|
||||
|
||||
<h4 id="item1.12">1.12</a>) 開発チームにはどのように参加しますか？</h4>
|
||||
<h4 id="item1.12">1.12</a>) パッチを提供したり、開発チーム参加するにはどうすればよいですか？</h4>
|
||||
|
||||
<p><a href="http://www.postgresql.org/docs/faqs.FAQ_DEV.html">
|
||||
（開発者向けの）Developer's FAQ</a>をごらんください。</p>
|
||||
@ -580,10 +589,7 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
<h4 id="item2.3">2.3</a>) PostgreSQL にグラフィカル・ユーザインターフェースはありますか？</h4>
|
||||
|
||||
|
||||
<p>もちろん、あります。
|
||||
詳細は、<a href="http://techdocs.postgresql.org/guides/GUITools">http://techdocs.postgresql.org/guides/GUITools</a>
|
||||
をごらんください。</p>
|
||||
|
||||
<p>商用とオープンソース開発者によるもの両方で、PostgreSQLには多くのGUIツールが利用可能で、詳細なリストは、<a href="http://www.postgresql.org/docs/techdocs.54">PostgreSQLコミュニティ文書</a> でごらんください。</p>
|
||||
|
||||
<hr />
|
||||
|
||||
@ -646,12 +652,13 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
|
||||
<dt><b>ハードウェアの選定</b></dt>
|
||||
|
||||
<dd>性能におけるハードウェアの影響は <a
|
||||
href="http://candle.pha.pa.us/main/writings/pgsql/hw_performance/index.html">
|
||||
http://candle.pha.pa.us/main/writings/pgsql/hw_performance/index.html</a>
|
||||
<dd>性能におけるハードウェアの影響は
|
||||
<a href="http://www.powerpostgresql.com/PerfList/">
|
||||
http://www.powerpostgresql.com/PerfList/</a> と、 <a
|
||||
href="http://momjian.us/main/writings/pgsql/hw_performance/index.html">
|
||||
http://momjian.us/main/writings/pgsql/hw_performance/index.html</a>
|
||||
(<a href="http://www.postgresql.jp/wg/psqltrans/hw_performance_j/index.html">JPUGサイトの日本語版</a>)
|
||||
と <a href="http://www.powerpostgresql.com/PerfList/">
|
||||
http://www.powerpostgresql.com/PerfList/</a> に述べられています。
|
||||
に述べられています。
|
||||
<br/>
|
||||
<br/>
|
||||
</dd>
|
||||
@ -680,16 +687,25 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
<i>max_connections</i> の値を変更して <i>postmaster</i>を再起動する
|
||||
ことで可能になります。</p>
|
||||
|
||||
<h4 id="item3.6">3.6</a>) PostgreSQLのメジャーリリースをアップデートするのにダンプとリストアをしなくてはならないのはなぜですか？</h4>
|
||||
<h4 id="item3.6">3.6</a>) PostgreSQLのアップグレードの手順はどうしますか？</h4>
|
||||
|
||||
<p>PostgreSQLチームはマイナーリリースでは小さな変更しか行ないません
|
||||
ので、7.4.0 から 7.4.1 へのアップグレードにはダンプとリストアの必要は
|
||||
ありません。しかし、メジャーリリース(たとえば、7.2から7.3へのような)
|
||||
では、システムテーブルやデータファイルの内部フォーマットの変更をしば
|
||||
しば行ないます。これらの変更はたいてい複雑で、そのため我々はデータファ
|
||||
イルのための後方互換性を維持することができません。ダンプは汎用フォー
|
||||
マットでデータを出力し、それを新しい内部フォーマットに読み込むことが
|
||||
できます。</p>
|
||||
<p>PostgreSQLチームはマイナーリリースではバグの修正しか行ないません
|
||||
ので、たとえば 7.4.8 から 7.4.9 へのアップグレードにダンプとリスト
|
||||
アは必要ありません。したがって、データベースサーバを一時的に停止して、
|
||||
アップデートしたバイナリをインストールし、そして、サーバをリスタート
|
||||
するだけです。</p>
|
||||
|
||||
<p>全ユーザはできるだけ早く最新のマイナーリリースにアップグレードす
|
||||
るべきです。すべてのアップグレードにリスクはつきものですが、
|
||||
PostgreSQLのマイナーリリースは、なるべく小さなリスクで一般的なバグの
|
||||
修正だけを目論んだものです。我々コミュニティの中ではアップグレード
|
||||
<i>しない</i>ほうがもっとリスクが高いものと考えられています。</p>
|
||||
|
||||
<p>しかし、メジャーリリース（たとえば、7.3 から 7.4 のような）では、
|
||||
システムテーブルやデータファイルの内部フォーマットの変更をしばしば行
|
||||
ないます。これらの変更はたいてい複雑で、そのため我々はデータファイル
|
||||
のための後方互換性を維持することができません。メジャーアップグレード
|
||||
のためには、データベースのダンプ/リロードが必要です。</p>
|
||||
|
||||
<h4 id="item3.7">3.7</a>) ハードウェアにはどんなコンピュータを使えばよいですか？</h4>
|
||||
|
||||
@ -790,7 +806,8 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
</p>
|
||||
|
||||
<p> デフォルトのブロックサイズを32kに増加することで、最大テーブルサイズ
|
||||
と行サイズと最大カラム数とを4倍にすることができます。</p>
|
||||
と行サイズと最大カラム数とを4倍にすることができます。また、最大テーブル
|
||||
サイズはテーブルパーティションを使って増やすこともできます。</p>
|
||||
|
||||
<p>ひとつの制限は、約2,000文字以上の長さのカラムにインデックスを付
|
||||
けることができないことです。 幸いにも、そのようなインデックスは実際
|
||||
@ -1061,21 +1078,21 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
|
||||
<p>PostgreSQLでつくられるすべてのロウは、<small>WITHOUT OIDS</small>
|
||||
でつくられないかぎり一意の<small>OID</small>を得ます。
|
||||
O<small>ID</small>は自動的に4バイトの整数で与えられ、それは、全イン
|
||||
<small>OID</small>は自動的に4バイトの整数で与えられ、それは、全イン
|
||||
ストレーションを通して一意な値となります。しかし、約40億でオーバーフ
|
||||
ローし、そして、O<small>ID</small>は重複をしはじめます。PostgreSQLは
|
||||
内部システムテーブルを一緒にリンクするためにO<small>ID</small> を使
|
||||
ローし、そして、<small>OID</small>は重複をしはじめます。PostgreSQLは
|
||||
内部システムテーブルを一緒にリンクするために<small>OID</small> を使
|
||||
います。
|
||||
|
||||
<p>ユーザのテーブルのカラムに一意の番号を付けるためには、
|
||||
O<small>ID</small> ではなく <small>SERIAL</small> を使うのが最もよい
|
||||
<small>OID</small> ではなく <small>SERIAL</small> を使うのが最もよい
|
||||
でしょう。<small>SERIAL</small>の連番は1つのテーブル内でのみ一意にな
|
||||
るからで、オーバーフローを起こしにくいと考えられます。
|
||||
8バイトのシーケンス値を保存するために、<small>SERIAL8</small>があり
|
||||
ます。</p>
|
||||
|
||||
<p>C<small>TID</small> は、特定の物理ロウをブロックとオフセットの値
|
||||
で識別するために使われます。C<small>TID</small>は、ロウが修正された
|
||||
<p><small>CTID</small> は、特定の物理ロウをブロックとオフセットの値
|
||||
で識別するために使われます。<small>CTID</small>は、ロウが修正された
|
||||
り再読込みされたときに変わります。また、物理ロウを差すためにインデッ
|
||||
クスの記載に使われます。</p>
|
||||
|
||||
@ -1237,7 +1254,7 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
[訳注：
|
||||
日本語版の製作については以下の通りです。
|
||||
|
||||
最終更新日: 2006年04月03日
|
||||
最終更新日: 2006年08月19日
|
||||
翻訳者: 桑村 潤 (<a href="mailto:juk at PostgreSQL.jp">Jun Kuwamura <juk at PostgreSQL.jp></a>)
|
||||
|
||||
このFAQの和訳の作成にあたり協力をしてくださった方々(敬称は略させていただきます):
|
||||
@ -1246,7 +1263,7 @@ http://www.postgresql.jp/PostgreSQL/references.html</a>
|
||||
石井 達夫(<a href="mailto:t-ishii at sra.co.jp">Tatsuo ISHII <t-ishii at sra.co.jp></a>)
|
||||
齊藤 知人(<a href="mailto:tomos at elelab.nsc.co.jp">Tomohito SAITOH <tomos at elelab.nsc.co.jp></a>)
|
||||
馬場 肇(<a href="mailto:baba at kusastro.kyoto-u.ac.jp">Hajime BABA <baba at kusastro.kyoto-u.ac.jp></a>)
|
||||
岡本 一幸(<a href="mailto:kaz-okamoto at hitachi-system.co.jp">Kazuyuki OKAMOTO <kokamoto at itg.hitachi.co.jp></a>)
|
||||
岡本 一幸(<a href="mailto:kaz-okamoto at hitachi-system.co.jp">Kazuyuki OKAMOTO <kaz-okamoto at hitachi-system.co.jp></a>)
|
||||
小菅 昭一(<a href="mailto:s-kosuge at str.hitachi.co.jp">Shoichi Kosuge <s-kosuge at str.hitachi.co.jp></a>)
|
||||
山下 義之(<a href="mailto:dica at eurus.dti.ne.jp">Yoshiyuki YAMASHITA <dica at eurus.dti.ne.jp></a>)
|
||||
境 真太郎(<a href="mailto:s_sakai at mxn.mesh.ne.jp">Sintaro SAKAI <s_sakai at mxn.mesh.ne.jp></a>)
|
||||
|
||||
@ -12,7 +12,7 @@
|
||||
<BODY bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000" alink="#0000ff">
|
||||
<H1>Ответы на часто задаваемые вопросы по PostgreSQL</H1>
|
||||
|
||||
<P>Дата последнего обновления: Пятница 24 февраля 23:28:40 EDT 2006</P>
|
||||
<P>Дата последнего обновления: Воскресенье 18 июня 15:33:25 EDT 2006</P>
|
||||
|
||||
<P>Английский вариант сопровождает: Брюс Момьян (Bruce Momjian) (<A href=
|
||||
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
|
||||
@ -34,14 +34,14 @@
|
||||
<A href="#item1.3">1.3</A>) Каковы авторские права на PostgreSQL?<BR>
|
||||
<A href="#item1.4">1.4</A>) На каких платформах работает PostgreSQL?<BR>
|
||||
<A href="#item1.5">1.5</A>) Где можно взять PostgreSQL?<BR>
|
||||
<A href="#item1.6">1.6</A>) Какая версия последняя?<BR>
|
||||
<A href="#item1.6">1.6</A>) Какая версия наиболее свежая?<BR>
|
||||
<A href="#item1.7">1.7</A>) Где получить поддержку?<BR>
|
||||
<A href="#item1.8">1.8</A>) Как мне сообщить об ошибке?<BR>
|
||||
<A href="#item1.9">1.9</A>) Как найти информацию об известных ошибках или отсутствующих
|
||||
возможностях?<BR>
|
||||
<A href="#item1.10">1.10</A>) Какая документация имеется в наличии?<BR>
|
||||
<A href="#item1.11">1.11</A>) Как научиться <SMALL>SQL</SMALL>?<BR>
|
||||
<A href="#item1.12">1.12</A>) Как присоединится к команде разработчиков?<BR>
|
||||
<A href="#item1.12">1.12</A>) Как мне отправить исправление или присоединится к команде разработчиков?<BR>
|
||||
<A href="#item1.13">1.13</A>) Как сравнить PostgreSQL с другими
|
||||
<SMALL>СУБД</SMALL>?<BR>
|
||||
|
||||
@ -64,8 +64,7 @@
|
||||
<A href="#item3.4">3.4</A>) Какие возможности для отладки есть в наличии?<BR>
|
||||
<A href="#item3.5">3.5</A>) Почему я получаю сообщение <I>"Sorry, too many
|
||||
clients"</I> когда пытаюсь подключиться к базе?<BR>
|
||||
<A href="#item3.6">3.6</A>) Почему необходимо делать dump и restore при
|
||||
обновлении выпусков PostgreSQL?<BR>
|
||||
<A href="#item3.6">3.6</A>) Как выполнить обновление PostgreSQL?<BR>
|
||||
<A href="#item3.7">3.7</A>) Какое компьютерное "железо" я должен
|
||||
использовать?<BR>
|
||||
|
||||
@ -222,9 +221,9 @@
|
||||
<A href="ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/</A>.</P>
|
||||
|
||||
|
||||
<H3><A name="item1.6">1.6</A>) Какая последняя версия?</H3>
|
||||
<H3><A name="item1.6">1.6</A>) Какая версия наиболее свежая?</H3>
|
||||
|
||||
<P>Последний выпуск PostgreSQL - это версия 8.1.3</P>
|
||||
<P>Последний выпуск PostgreSQL - это версия 8.1.4</P>
|
||||
|
||||
<P>Мы планируем выпускать новые старшие версии каждый год,
|
||||
а младшие версии каждые несколько месяцев.</P>
|
||||
@ -369,14 +368,20 @@
|
||||
Bowman, Judith S., et al., Addison-Wesley. Другим нравится <I>The
|
||||
Complete Reference SQL</I>, Groff et al., McGraw-Hill.</P>
|
||||
|
||||
Есть прекрасный учебник на <A href=
|
||||
"http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
|
||||
на <A href="http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
|
||||
http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,</A>
|
||||
и на <A href="http://sqlcourse.com/">http://sqlcourse.com.</A></P>
|
||||
<P>Существует также множество прекрасных учебников доступных в online:
|
||||
<UL>
|
||||
<LI><A href="http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
|
||||
</LI>
|
||||
<LI><A href="http://sqlcourse.com/">http://sqlcourse.com.</A>
|
||||
</LI>
|
||||
<LI><A href="http://www.w3schools.com/sql/default.asp">http://www.w3school.com/sql/default.asp</A>
|
||||
</LI>
|
||||
<LI><A href="http://mysite.verizon.net/Graeme_Birchall/id1.html">http://mysite.verizon.net/Graeme_Birchall/id1.html</A>
|
||||
</LI>
|
||||
</UL>
|
||||
</P>
|
||||
|
||||
|
||||
<H3><A name="item1.12">1.12</A>) Как присоединится к команде разработчиков?</H3>
|
||||
<H3><A name="item1.12">1.12</A>) Как мне прислать исправление или присоединится к команде разработчиков?</H3>
|
||||
|
||||
<P>Смотрите <a href="http://www.postgresql.org/docs/faqs.FAQ_DEV.html">
|
||||
FAQ для разработчиков</A>.</P>
|
||||
@ -483,8 +488,10 @@
|
||||
<H3><A name="item2.3">2.3</A>) Есть ли у PostgreSQL графический интерфейс
|
||||
пользователя?</H3>
|
||||
|
||||
<P>Да, подробности смотрите в <a href="http://techdocs.postgresql.org/guides/GUITools">
|
||||
http://techdocs.postgresql.org/guides/GUITools</A>.</P>
|
||||
<P>Для PostgreSQL существует большое количество инструментов с
|
||||
графическим интерфейсом как коммерческих, так и открытых. Подробности
|
||||
можно найти в <a href="http://www.postgresql.org/docs/techdocs.54">
|
||||
Документации сообщества PostgreSQL</A></P>
|
||||
|
||||
<HR>
|
||||
|
||||
@ -549,7 +556,7 @@
|
||||
<DT><B>Выбор "железа" - аппаратного обеспечения</B></DT>
|
||||
|
||||
<DD>Влияние "железа" на производительность подробно описано в
|
||||
<A href="http://candle.pha.pa.us/main/writings/pgsql/hw_performance/index.html">
|
||||
<A href="http://momjian.us/main/writings/pgsql/hw_performance/index.html">
|
||||
http://candle.pha.pa.us/main/writings/pgsql/hw_performance/index.html</A> и
|
||||
<A href="http://www.powerpostgresql.com/PerfList/">
|
||||
http://www.powerpostgresql.com/PerfList/</A>.
|
||||
@ -576,24 +583,27 @@
|
||||
и перестартовать <I>postmaster</I>.</P>
|
||||
|
||||
|
||||
<H3><A name="item3.6">3.6</A>) Почему необходимо делать dump и restore при
|
||||
обновлении выпусков PostgreSQL?</H3>
|
||||
<H3><A name="item3.6">3.6</A>) Как выполнить обновление PostgreSQL?</H3>
|
||||
|
||||
<P>Разработчики PostgreSQL делают только небольшие изменения между
|
||||
подвыпусками. Таким образом обновление с версии 7.4.0 до 7.4.1 не требует
|
||||
выполнения dump и restore. Однако при выходе очередного выпуска
|
||||
<P>Между подвыпусками, разработчики PostgreSQL делают только исправления
|
||||
ошибок. Таким образом обновление с версии 7.4.8 до 7.4.9 не требует
|
||||
выполнения dump и restore; достаточно остановить сервер, установить
|
||||
обновлённые файлы СУБД и запустить сервер.</P>
|
||||
|
||||
<P>Все пользователи должны бы обновляться на наиболее свежую подверсию
|
||||
как только она будет доступна. В то время как каждое обновление
|
||||
подразумевает некоторый риск, подверсии PostgreSQL разрабытываются только
|
||||
для исправления общих ошибок с минимальным риском. Таким образом, ваш
|
||||
риск связан только с самим обновлением.</P>
|
||||
|
||||
|
||||
<P>При выходе очередного выпуска
|
||||
(т.е. при обновлении например, с 7.3 на 7.4) часто меняется внутренний
|
||||
формат системных таблиц и файлов данных. Эти изменения часто носят
|
||||
комплексный характер, так что нет возможности обеспечить обратную
|
||||
совместимость файлов данных. Выполение dump позволяет получить данные
|
||||
в общем формате, который затем может быть загружен при использовании
|
||||
нового внутреннего формата.</P>
|
||||
сложный характер, так что мы не обслуживаем обратную
|
||||
совместимость для файлов данных. В этих случаях для обновления базы
|
||||
данных требуется выполнить dump/restore.</P>
|
||||
|
||||
<P>В тех выпусках, где формат данных на диске не меняется, для проведения
|
||||
обновления может быть использован сценарий <i>pg_upgrade</i> без
|
||||
использования dump/restore. Комментарии к выпуску говорит когда можно
|
||||
использовать <i>pg_upgrade</i> для этого выпуска.</P>
|
||||
|
||||
|
||||
<H3><A name="item3.7">3.7</A>) Какое компьютерное "железо" я должен
|
||||
использовать?</H3>
|
||||
@ -684,7 +694,7 @@
|
||||
</TR>
|
||||
<TR>
|
||||
<TD>Максимальный размер строки?</TD>
|
||||
<TD>1.6 TB</TD>
|
||||
<TD>400 Gb</TD>
|
||||
</TR>
|
||||
<TR>
|
||||
<TD>Максимальный размер поля?</TD>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user