mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
Backpatch FAQs to 8.1.X.
This commit is contained in:
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.
|
||||
|
Reference in New Issue
Block a user