Skip to content

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

Prepare for final release.

parent 9ceaa677
Show whitespace changes
Inline Side-by-side
Showing with 1070 additions and 864 deletions
HISTORY
View file @ f0410b1e
PostgreSQL 6.3 Sun Feb 1 14:57:30 EST 1998 PostgreSQL 6.3 Sun Mar 1 14:57:30 EST 1998
------------------------------------------------------------- -------------------------------------------------------------
A dump/restore is required for those wishing to migrate data from A dump/restore is required for those wishing to migrate data from
...@@ -39,16 +39,16 @@ Generate elog(ERROR) on over-large integer(Bruce) ...@@ -39,16 +39,16 @@ Generate elog(ERROR) on over-large integer(Bruce)
Allow multiple-argument functions in constraint clauses(Thomas) Allow multiple-argument functions in constraint clauses(Thomas)
Check boolean input literals for 'true','false','yes','no','1','0' Check boolean input literals for 'true','false','yes','no','1','0'
and throw elog(ERROR) if unrecognized(Thomas) and throw elog(ERROR) if unrecognized(Thomas)
Change default table creation from ACL_RD to ACL_NO (aka private tables)(marc) Major large objects fix
Enhancements Enhancements
------------ ------------
Subselects with EXISTS, IN, ALL, ANY keywords (Vadim, Bruce, Thomas)
New User Manual(Thomas, others)
Speedup by inlining some frequently-called functions
Real deadlock detection, no more timeouts(Bruce) Real deadlock detection, no more timeouts(Bruce)
<NOT DONE YET> Subselects with EXISTS, IN, ALL, ANY keywords (Vadim, Bruce, Thomas)
Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
CURRENT_USER(Thomas) CURRENT_USER(Thomas)
Speedup by inlining some frequently-called functions
Modify constraint syntax to be SQL92-compliant(Thomas) Modify constraint syntax to be SQL92-compliant(Thomas)
Implement SQL92 PRIMARY KEY and UNIQUE clauses using indices(Thomas) Implement SQL92 PRIMARY KEY and UNIQUE clauses using indices(Thomas)
Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas) Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
...@@ -107,7 +107,6 @@ Add UNION, GROUP, DISTINCT to INSERT(Bruce) ...@@ -107,7 +107,6 @@ Add UNION, GROUP, DISTINCT to INSERT(Bruce)
varchar() stores only necessary bytes on disk(Bruce) varchar() stores only necessary bytes on disk(Bruce)
Fix for BLOBs(Peter) Fix for BLOBs(Peter)
Mega-Patch for JDBC...see README_6.3 for list of changes(Peter) Mega-Patch for JDBC...see README_6.3 for list of changes(Peter)
Allow installation data block size and max tuple size configuration(Darren)
Remove unused "option" from PQconnectdb() Remove unused "option" from PQconnectdb()
New LOCK command and lock manual page describing deadlocks(Bruce) New LOCK command and lock manual page describing deadlocks(Bruce)
Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce) Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce)
...@@ -122,8 +121,17 @@ Add Unix socket support to DBD::Pg(Goran) ...@@ -122,8 +121,17 @@ Add Unix socket support to DBD::Pg(Goran)
New python interface (PyGreSQL 2.0)(D'Arcy) New python interface (PyGreSQL 2.0)(D'Arcy)
New frontend/backend protocol has a version number, network byte order(Phil) New frontend/backend protocol has a version number, network byte order(Phil)
Security features in pg_hba.conf enhanced and documented, many cleanups(Phil) Security features in pg_hba.conf enhanced and documented, many cleanups(Phil)
New HTML and Postscript documentation(Thomas) CHAR() now faster access than VARCHAR() or TEXT
ecpg embedded SQL preprocessor
Add GROUP BY to INSERT INTO table SELECT * FROM table2
Reduce system column overhead(Vadmin)
Remove pg_time table(Vadim)
Add pg_type attribute to identify types that need length (bpchar, varchar)
Add report of offending line when COPY command fails
Allow VIEW permissions to be set separately from the underlying tables.
For security, use GRANT/REVOKE on views as appropriate(Jan)
Tables now have no default GRANT SELECT TO PUBLIC. You must
explicitly grant such permissions.
Source Tree Changes Source Tree Changes
------------------- -------------------
...@@ -160,6 +168,7 @@ Start an AUX port ...@@ -160,6 +168,7 @@ Start an AUX port
Start a Cygnus port Start a Cygnus port
Add string functions to regression suite(Thomas) Add string functions to regression suite(Thomas)
Expand a few function names formerly truncated to 16 characters(Thomas) Expand a few function names formerly truncated to 16 characters(Thomas)
Remove un-needed malloc() calls and replace with palloc()(Bruce)
PostgreSQL 6.2.1 Fri Oct 17 00:01:27 EDT 1997 PostgreSQL 6.2.1 Fri Oct 17 00:01:27 EDT 1997
......
doc/FAQ
View file @ f0410b1e
<HTML>
<HEAD>
<TITLE>PostgreSQL FAQ</title>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#FF0000" VLINK="#A00000" ALINK="#0
000FF">
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
Last updated: Sun Feb 1 16:13:28 EST 1998 <P>
Last updated: Wed Feb 25 14:37:07 EST 1998
Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us) <P>
Current maintainer: Bruce Momjian (<a
The most recent version of this document can be viewed at the postgreSQL Web href="mailto:maillist@candle.pha.pa.us">maillist@candle.pha.pa.us</a>)<BR>
site, http://postgreSQL.org. <P>
The most recent version of this document can be viewed at
the postgreSQL Web site, <a
href="http://postgreSQL.org">http://postgreSQL.org</a>.
<P>
Linux-specific questions are answered in Linux-specific questions are answered in
http://postgreSQL.org/docs/faq-linux.shtml. <a href="http://postgreSQL.org/docs/faq-linux.shtml">http://postgreSQL.org/docs
/faq-linux.shtml</a>.
<P>
Irix-specific questions are answered in Irix-specific questions are answered in
http://postgreSQL.org/docs/faq-irix.shtml. <a href="http://postgreSQL.org/docs/faq-irix.shtml">http://postgreSQL.org/docs/
faq-irix.shtml</a>.
------------------------------------------------------------------------ <P>
<HR>
Questions answered: <P>
<H2>Questions answered:</H2>
1) General questions <H3> 1) General questions</H3>
<a href="#1.1">1.1</a>) What is PostgreSQL?<BR>
1.1) What is PostgreSQL? <a href="#1.2">1.2</a>) What does PostgreSQL run on?<BR>
1.2) What does PostgreSQL run on? <a href="#1.3">1.3</a>) Where can I get PostgreSQL?<BR>
1.3) Where can I get PostgreSQL? <a href="#1.4">1.4</a>) What's the copyright on PostgreSQL?<BR>
1.4) What's the copyright on PostgreSQL? <a href="#1.5">1.5</a>) Support for PostgreSQL<BR>
1.5) Support for PostgreSQL <a href="#1.6">1.6</a>) Latest release of PostgreSQL<BR>
1.6) Latest release of PostgreSQL <a href="#1.7">1.7</a>) Is there a commercial version of PostgreSQL?<BR>
1.7) Is there a commercial version of PostgreSQL? <a href="#1.8">1.8</a>) What documentation is available for PostgreSQL?<BR>
1.8) What documentation is available for PostgreSQL? <a href="#1.9">1.9</a>) What version of SQL does PostgreSQL use?<BR>
1.9) What version of SQL does PostgreSQL use? <a href="#1.10">1.10</a>) Does PostgreSQL work with databases from
1.10) Does PostgreSQL work with databases from earlier versions of postgres? earlier versions of postgres?<BR>
1.11) Are there ODBC drivers for PostgreSQL? <a href="#1.11">1.11</a>) Are there ODBC drivers for
1.12) What tools are available for hooking postgres to Web pages? PostgreSQL?<BR>
1.13) Does PostgreSQL have a graphical user interface? A report generator? A <a href="#1.12">1.12</a>) What tools are available for hooking
embedded query language interface? postgres to Web pages?<BR>
1.14) What is a good book to learn SQL? <a href="#1.13">1.13</a>) Does PostgreSQL have a graphical user interface
?
2) Installation/Configuration questions A report generator? A embedded query language interface?<BR>
<a href="#1.14">1.14</a>) What is a good book to learn SQL?<BR>
2.1) initdb doesn't run
2.2) when I start up the postmaster, I get "FindBackend: could not find a <H3> 2) Installation/Configuration questions</H3>
backend to execute..." "postmaster: could not find backend to execute..." <a href="#2.1">2.1</a>) initdb doesn't run<BR>
2.3) The system seems to be confused about commas, decimal points, and date <a href="#2.2">2.2</a>) when I start up the postmaster, I get
formats. "FindBackend: could not find a backend to execute..."
2.4) How do I install PostgreSQL somewhere other than /usr/local/pgsql? "postmaster: could not find backend to execute..."<BR>
2.5) When I run postmaster, I get a Bad System Call core dumped message. <a href="#2.3">2.3</a>) The system seems to be confused about commas,
2.6) When I try to start the postmaster, I get IpcMemoryCreate errors. decimal points, and date formats.<BR>
2.7) I have changed a source file, but a recompile does not see the change? <a href="#2.4">2.4</a>) How do I install PostgreSQL somewhere other than
2.8) How do I prevent other hosts from accessing my PostgreSQL /usr/local/pgsql?<BR>
2.9) I can't access the database as the 'root' user. <a href="#2.5">2.5</a>) When I run postmaster, I get a Bad System Call
2.10) All my servers crash under concurrent table access. Why? core dumped message.<BR>
2.11) How do I tune the database engine for better performance? <a href="#2.6">2.6</a>) When I try to start the postmaster, I get
2.12) What debugging features are available in PostgreSQL? IpcMemoryCreate errors.<BR>
2.13) How do I enable more than 32 concurrent backends? <a href="#2.7">2.7</a>) I have changed a source file, but a
recompile does not see the change?<BR>
3) Operational questions <a href="#2.8">2.8</a>) How do I prevent other hosts from accessing my
PostgreSQL<BR>
3.1) Does PostgreSQL support nested subqueries? <a href="#2.9">2.9</a>) I can't access the database as the
3.2) I've having a lot of problems using rules. 'root' user.<BR>
3.3) I can't seem to write into the middle of large objects reliably. <a href="#2.10">2.10</a>) All my servers crash under concurrent
3.4) How can I write client applications to PostgreSQL? table access. Why?<BR>
3.5) How do I set up a pg_group? <a href="#2.11">2.11</a>) How do I tune the database engine for
3.6) What is the exact difference between binary cursors and normal cursors? better performance?<BR>
3.7) What is a R-tree index and what is it used for? <a href="#2.12">2.12</a>) What debugging features are available in
3.8) What is the maximum size for a tuple? PostgreSQL?<BR>
3.9) I defined indices but my queries don't seem to make use of them. Why? <a href="#2.13">2.13</a>) How do I enable more than 32 concurrent
3.10) How do I do regular expression searches? case-insensitive regexp backends?
searching? <H3> 3) Operational questions</H3>
3.11) I experienced a server crash during a vacuum. How do I remove the lock <a href="#3.1">3.1</a>) Does PostgreSQL support nested subqueries?<BR>
file? <a href="#3.2">3.2</a>) I've having a lot of problems using rules.<BR>
3.12) What is the difference between the various character types? <a href="#3.3">3.3</a>) I can't seem to write into the middle of large
3.13) In a query, how do I detect if a field is NULL? objects reliably.<BR>
3.14) How do I see how the query optimizer is evaluating my query? <a href="#3.4">3.4</a>) How can I write client applications to
3.15) How do I create a serial field? PostgreSQL?<BR>
3.16) What are the pg_psort.XXX files in my database directory? <a href="#3.5">3.5</a>) How do I set up a pg_group?<BR>
3.17) Why can't I connect to my database from another machine? <a href="#3.6">3.6</a>) What is the exact difference between
3.18) How do I find out what indexes or operations are defined in the binary cursors and normal cursors?<BR>
database? <a href="#3.7">3.7</a>) What is a R-tree index and what is it
3.19) What is the time-warp feature and how does it relate to vacuum? used for?<BR>
3.20) What is an oid? What is a tid? <a href="#3.8">3.8</a>) What is the maximum size for a
3.21) What is the meaning of some of the terms used in Postgres? tuple?<BR>
3.22) What is Genetic Query Optimization? <a href="#3.9">3.9</a>) I defined indices but my queries don't
3.23) How do you remove a column from a table? seem to make use of them. Why?<BR>
3.24) How do SELECT only the first few rows of a query? <a href="#3.10">3.10</a>) How do I do regular expression searches?
3.25) Why can't I create a column named "time"? case-insensitive regexp searching?<BR>
3.26) How much database disk space is required to store data from a typical <a href="#3.11">3.11</a>) I experienced a server crash during a
flat file? vacuum. How do I remove the lock file?<BR>
<a href="#3.12">3.12</a>) What is the difference between the
4) Questions about extending PostgreSQL various character types?<BR>
<a href="#3.13">3.13</a>) In a query, how do I detect if a field
4.1) I wrote a user-defined function and when I run it in psql, it dumps is NULL?<BR>
core. <a href="#3.14">3.14</a>) How do I see how the query optimizer is
4.2) I get messages of the type NOTICE:PortalHeapMemoryFree: 0x402251d0 evaluating my query?<BR>
4.3) I've written some nifty new types and functions for PostgreSQL. <a href="#3.15">3.15</a>) How do I create a serial field?<BR>
4.4) How do I write a C function to return a tuple? <a href="#3.16">3.16</a>) What are the pg_psort.XXX files in my
database directory?<BR>
5) Bugs <a href="#3.17">3.17</a>) Why can't I connect to my database from
another machine?<BR>
5.1) How do I make a bug report? <a href="#3.18">3.18</a>) How do I find out what indexes or
operations are defined in the database?<BR>
------------------------------------------------------------------------ <a href="#3.19">3.19</a>) What is the time-warp feature and how
does it relate to vacuum?<BR>
Section 1: General Questions <a href="#3.20">3.20</a>) What is an oid? What is a tid?<BR>
<a href="#3.21">3.21</a>) What is the meaning of some of the terms
1.1) What is PostgreSQL? used in Postgres?<BR>
<a href="#3.22">3.22</a>) What is Genetic Query Optimization?<BR>
PostgreSQL is an enhancement of the POSTGRES database management system, a <a href="#3.23">3.23</a>) How do you remove a column from a table?<BR>
next-generation DBMS research prototype. While PostgreSQL retains the <a href="#3.24">3.24</a>) How do SELECT only the first few rows of
a query?<BR>
<a href="#3.25">3.25</a>) Why can't I create a column named "time"?<BR>
<a href="#3.26">3.26</a>) How much database disk space is required
to store data from a typical flat file?<BR>
<H3> 4) Questions about extending PostgreSQL</H3>
<a href="#4.1">4.1</a>) I wrote a user-defined function and when I run
it in psql, it dumps core.<BR>
<a href="#4.2">4.2</a>) I get messages of the type
NOTICE:PortalHeapMemoryFree: 0x402251d0<BR>
<a href="#4.3">4.3</a>) I've written some nifty new types and functions
for PostgreSQL.<BR>
<a href="#4.4">4.4</a>) How do I write a C function to return a
tuple?<BR>
<H3> 5) Bugs</H3>
<a href="#5.1">5.1</a>) How do I make a bug report?
<P>
<HR>
<H2> Section 1: General Questions</H2> <H3><a
name="1.1">1.1</a>) What is PostgreSQL?</H3>
<P>
PostgreSQL is an enhancement of the POSTGRES database management system,
a next-generation DBMS research prototype. While PostgreSQL retains the
powerful data model and rich data types of POSTGRES, it replaces the powerful data model and rich data types of POSTGRES, it replaces the
PostQuel query language with an extended subset of SQL. PostgreSQL is free PostQuel query language with an extended subset of SQL. PostgreSQL is
and the complete source is available. free and the complete source is available.
<P>
PostgreSQL development is being performed by a team of Internet developers PostgreSQL development is being performed by a team of Internet
who all subscribe to the PostgreSQL development mailing list. The current developers who all subscribe to the PostgreSQL development mailing list.
coordinator is Marc G. Fournier (scrappy@postgreSQL.org). (See below on how The current coordinator is Marc G. Fournier (<a
to join). This team is now responsible for all current and future href="mailto:scrappy@postgreSQL.org">scrappy@postgreSQL.org</a>). (See
development of PostgreSQL. below on how to join). This team is now responsible for all current and
future development of PostgreSQL.
The authors of PostgreSQL 1.01 were Andrew Yu and Jolly Chen. Many others <P>
have contributed to the porting, testing, debugging and enhancement of the The authors of PostgreSQL 1.01 were Andrew Yu and Jolly Chen. Many
code. The original Postgres code, from which PostgreSQL is derived, was the others have contributed to the porting, testing, debugging and
effort of many graduate students, undergraduate students, and staff enhancement of the code. The original Postgres code, from which
programmers working under the direction of Professor Michael Stonebraker at PostgreSQL is derived, was the effort of many graduate students,
the University of California, Berkeley. undergraduate students, and staff programmers working under the
direction of Professor Michael Stonebraker at the University of
California, Berkeley.
<P>
The original name of the software at Berkeley was Postgres. When SQL The original name of the software at Berkeley was Postgres. When SQL
functionality was added in 1995, its name was changed to Postgres95. The functionality was added in 1995, its name was changed to Postgres95. The
name was changed at the end of 1996 to PostgreSQL. name was changed at the end of 1996 to PostgreSQL.
<P>
1.2) What does PostgreSQL run on? <H3><a name="1.2">1.2</a>) What does PostgreSQL run
on?</H3>
<P>
The authors have compiled and tested PostgreSQL on the following The authors have compiled and tested PostgreSQL on the following
platforms(some of these compiles require gcc 2.7.0): platforms(some of these compiles require gcc 2.7.0):
<UL>
* aix - IBM on AIX 3.2.5 or 4.x <LI> aix - IBM on AIX 3.2.5 or 4.x
* alpha - DEC Alpha AXP on Digital Unix 2.0, 3.2, 4.0 <LI> alpha - DEC Alpha AXP on Digital Unix 2.0, 3.2, 4.0
* BSD44_derived - OSs derived from 4.4-lite BSD (NetBSD, FreeBSD) <LI> BSD44_derived - OSs derived from 4.4-lite BSD (NetBSD, FreeBSD)
* bsdi - BSD/OS 2.0, 2.01, 2.1, 3.0 <LI> bsdi - BSD/OS 2.0, 2.01, 2.1, 3.0
* dgux - DG/UX 5.4R4.11 <LI> dgux - DG/UX 5.4R4.11
* hpux - HP PA-RISC on HP-UX 9.0, 10 <LI> hpux - HP PA-RISC on HP-UX 9.0, 10
* i386_solaris - i386 Solaris <LI> i386_solaris - i386 Solaris
* irix5 - SGI MIPS on IRIX 5.3 <LI> irix5 - SGI MIPS on IRIX 5.3
* linux - Intel x86 on Linux 2.0 and Linux ELF SPARC on Linux ELF PPC on <LI> linux - Intel x86 on Linux 2.0 and Linux ELF
Linux Elf (For non-ELF Linux, see LINUX_ELF below). SPARC on Linux ELF
* sco - SCO 3.2v5 PPC on Linux Elf
* sparc_solaris - SUN SPARC on Solaris 2.4, 2.5, 2.5.1 (For non-ELF Linux, see LINUX_ELF below).
* sunos4 - SUN SPARC on SunOS 4.1.3 <LI> sco - SCO 3.2v5
* svr4 - Intel x86 on Intel SVR4 and MIPS <LI> sparc_solaris - SUN SPARC on Solaris 2.4, 2.5, 2.5.1
* ultrix4 - DEC MIPS on Ultrix 4.4 <LI> sunos4 - SUN SPARC on SunOS 4.1.3
<LI> svr4 - Intel x86 on Intel SVR4 and MIPS
<LI> ultrix4 - DEC MIPS on Ultrix 4.4
</UL>
The following platforms have known problems/bugs: The following platforms have known problems/bugs:
<UL>
* nextstep - Motorola MC68K or Intel x86 on NeXTSTEP 3.2 <LI> nextstep - Motorola MC68K or Intel x86 on NeXTSTEP 3.2
</UL>
1.3) Where can I get PostgreSQL? <P>
<H3><a name="1.3">1.3</a>) Where can I get PostgreSQL?</H3>
The primary anonymous ftp site for PostgreSQL is: <P> The primary anonymous ftp site for PostgreSQL is:
<UL>
* ftp://ftp.postgreSQL.org/pub <LI> <a
href="ftp://ftp.postgreSQL.org/pub">ftp://ftp.postgreSQL.org/pub</a>
A mirror site exists at: </UL>
<P> A mirror site exists at:
* ftp://postgres95.vnet.net/pub/postgres95 <UL>
* ftp://ftp.luga.or.at/pub/postgres95 <LI> <a
* ftp://cal011111.student.utwente.nl/pub/postgres95 href="ftp://postgres95.vnet.net/pub/postgres95">ftp://postgres95.vnet.net/pub/p
* ftp://ftp.uni-trier.de/pub/database/rdbms/postgres/postgres95 ostgres95</a>
* ftp://rocker.sch.bme.hu <LI> <a
href="ftp://ftp.luga.or.at/pub/postgres95">ftp://ftp.luga.or.at/pub/postgres95<
1.4) What's the copyright on PostgreSQL? /a>
<LI> <a
href="ftp://cal011111.student.utwente.nl/pub/postgres95">ftp://cal011111.studen
t.utwente.nl/pub/postgres95</a>
<LI> <a
href="ftp://ftp.uni-trier.de/pub/database/rdbms/postgres/postgres95">ftp://ftp.
uni-trier.de/pub/database/rdbms/postgres/postgres95</a>
<LI> <a
href="ftp://rocker.sch.bme.hu">ftp://rocker.sch.bme.hu</a>
</UL>
<H3><a name="1.4">1.4</a>) What's the copyright on
PostgreSQL?</H3>
<P>
PostgreSQL is subject to the following COPYRIGHT. PostgreSQL is subject to the following COPYRIGHT.
<P>
PostgreSQL Data Base Management System PostgreSQL Data Base Management System
<P>
Copyright (c) 1994-6 Regents of the University of California Copyright (c) 1994-6 Regents of the University of California
<P>
Permission to use, copy, modify, and distribute this software and its Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement documentation for any purpose, without fee, and without a written
is hereby granted, provided that the above copyright notice and this agreement is hereby granted, provided that the above copyright notice
paragraph and the following two paragraphs appear in all copies. and this paragraph and the following two paragraphs appear in all
copies.
IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR <P>
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY
LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES,
EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS
SUCH DAMAGE. DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
<P>
THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER
"AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
MODIFICATIONS.
1.5) Support for PostgreSQL <P>
<H3><a name="1.5">1.5</a>) Support for PostgreSQL </H3>
There is no official support for PostgreSQL from the original maintainers or <P>
from University of California, Berkeley. It is maintained through volunteer There is no official support for PostgreSQL from the original
effort only. maintainers or from University of California, Berkeley. It is
maintained through volunteer effort only.
The main mailing list is: questions@postgreSQL.org. It is available for <P>
discussion o f matters pertaining to PostgreSQL, including but not limited The main mailing list is: <a
to bug reports and fixes. For info on how to subscribe, send a mail with the href="mailto:questions@postgreSQL.org">questions@postgreSQL.org</a>. It
lines in the body (not the subject line) is available for discussion o f matters pertaining to PostgreSQL,
including but not limited to bug reports and fixes. For info on how to
subscribe, send a mail with the lines in the body (not the subject line)
<PRE>
<CODE>
subscribe subscribe
end end
</CODE>
to questions-request@postgreSQL.org. </PRE>
<P>
There is also a digest list available. To subscribe to this list, send email to <a
to: questions-digest-request@postgreSQL.org with a BODY of: href="mailto:questions-request@postgreSQL.org">questions-request@postgreSQL.org
</a>.
<P>
There is also a digest list available. To subscribe to this list, send
email to:
<a
href="mailto:questions-digest-request@postgreSQL.org">
questions-digest-request@postgreSQL.org</a> with a BODY of:
<PRE>
<KBD>
subscribe subscribe
end end
</KBD>
</PRE>
Digests are sent out to members of this list whenever the main list has Digests are sent out to members of this list whenever the main list has
received around 30k of messages. received around 30k of messages.
<P>
There is a bugs mailing list available. To subscribe to this list, send There is a bugs mailing list available. To subscribe to this
email to bugs-request@postgreSQL.org with a BODY of: list, send email to <a
href="mailto:bugs-request@postgreSQL.org">bugs-request@postgreSQL.org</a>
There is also a developers discussion mailing list available. To subscribe with a BODY of:
to this list, send email to hackers-request@postgreSQL.org with a BODY of: <P>
There is also a developers discussion mailing list available. To subscribe to
this
list, send email to <a
href="mailto:hackers-request@postgreSQL.org">hackers-request@postgreSQL.org</a>
with a BODY of:
<P>
<PRE>
<KBD>
subscribe subscribe
end end
</KBD>
Additional information about PostgreSQL can be found via the PostgreSQL WWW </PRE>
home page at: <P>
Additional information about PostgreSQL can be found via the PostgreSQL
http://postgreSQL.org WWW home page at:
<BLOCKQUOTE>
1.6) Latest release of PostgreSQL <a
href="http://postgreSQL.org">http://postgreSQL.org</a>
</BLOCKQUOTE>
<P>
<H3><a name="1.6">1.6</a>) Latest release of PostgreSQL</H3>
<P>
The latest release of PostgreSQL is version 6.2.1, which was released on The latest release of PostgreSQL is version 6.2.1, which was released on
October 17th, 1997. We are testing 6.3 beta. For information about what is October 17th, 1997. We are testing 6.3 beta. For information about
new in 6.3, see our TODO list on our WWW page. what is new in 6.3, see our TODO list on our WWW page.
<P>
We plan to have major releases every three months. We plan to have major releases every three months.
<P>
1.7) Is there a commercial version of PostgreSQL? <H3><a name="1.7">1.7</a>) Is there a commercial version of PostgreSQL?</H
3>
<P>
Illustra Information Technology (a wholly owned subsidiary of Informix Illustra Information Technology (a wholly owned subsidiary of Informix
Software, Inc.) sells an object-relational DBMS called Illustra that was Software, Inc.) sells an object-relational DBMS called Illustra that was
originally based on postgres. Illustra has cosmetic similarities to originally based on postgres. Illustra has cosmetic similarities to
PostgreSQL but has more features, is more robust, performs better, and PostgreSQL but has more features, is more robust, performs better, and
offers real documentation and support. On the flip side, it costs money. For offers real documentation and support. On the flip side, it costs
more information, contact sales@illustra.com money. For more information, contact <a
href="mailto:sales@illustra.com">sales@illustra.com</a>
1.8) What documentation is available for PostgreSQL? <P>
<H3><a name="1.8">1.8</a>) What documentation is available for PostgreSQL?
A user manual, manual pages, and some small test examples are included in </H3>
the distribution. The sql and built-in manual pages are particularly <P>
A user manual, manual pages, and some small test examples are included
in the distribution. The sql and built-in manual pages are particularly
important. important.
<P>
The www page contains pointers to an implementation guide and five papers The www page contains pointers to an implementation guide and five
written about postgres design concepts and features. papers written about postgres design concepts and features.
<P>
1.9) What version of SQL does PostgreSQL use? <H3><a name="1.9">1.9</a>) What version of SQL does PostgreSQL use?</H3>
<P>
PostgreSQL supports a subset of SQL-92. It has most of the important PostgreSQL supports a subset of SQL-92. It has most of the important
constructs but lacks some of the functionality. The most visible differences constructs but lacks some of the functionality. The most visible
are: differences are:
<UL>
* no support for nested subqueries <LI> no HAVING clause under a GROUP BY
* no HAVING clause under a GROUP BY </UL>
<P>
On the other hand, you get to create user-defined types, functions, On the other hand, you get to create user-defined types, functions,
inheritance etc. If you're willing to help with PostgreSQL coding, inheritance etc.
eventually we can also add the missing features listed above. <P>
<H3><a name="1.10">1.10</a>) Does PostgreSQL work with databases from
1.10) Does PostgreSQL work with databases from earlier versions of postgres? earlier versions of postgres?</H3>
<P>
PostgreSQL v1.09 is compatible with databases created with v1.01. PostgreSQL v1.09 is compatible with databases created with v1.01.
<P>
Upgrading to 6.3 from earlier releases requires a dump and restore. Upgrading to 6.3 from earlier releases requires a dump and restore.
<P>
Upgrading to 6.2.1 from pre-6.2 requires a dump and restore. Upgrading to 6.2.1 from pre-6.2 requires a dump and restore.
<P>
Upgrading to 6.2.1 from 6.2 does not require a dump, but see the appropriate Upgrading to 6.2.1 from 6.2 does not require a dump, but see the
/migration file in the distribution. appropriate /migration file in the distribution.
<P>
Those ugrading from versions earlier than 1.09 must upgrade to 1.09 first Those ugrading from versions earlier than 1.09 must upgrade to 1.09
without a dump/reload, then dump the data from 1.09, and then load it into first without a dump/reload, then dump the data from 1.09, and then load
6.2.1 or 6.3 beta. it into 6.2.1 or 6.3 beta.
<P>
1.11) Are there ODBC drivers for PostgreSQL? <H3><a name="1.11">1.11</a>) Are there ODBC drivers for PostgreSQL?</H3>
<P>
There are two ODBC drivers available, PostODBC and OpenLink ODBC. There are two ODBC drivers available, PostODBC and OpenLink ODBC.
<P>
For all people being interested in PostODBC, there are now two mailing lists PostODBC is included in the distribution.
devoted to the discussion of PostODBC. The mailing lists are: For all people being interested in PostODBC, there are now two mailing
lists devoted to the discussion of PostODBC. The mailing lists are:
* postodbc-users@listserv.direct. net <UL>
* postodbc-developers@listse rv.direct.net <LI> <a
href="mailto:postodbc-users@listserv.direct.net">postodbc-users@listserv.direct
.
net</a>
<LI> <a
href="mailto:postodbc-developers@listserv.direct.net">postodbc-developers@lists
e
rv.direct.net</a>
</UL>
<P>
these lists are ordinary majordomo mailing lists. You can subscribe by these lists are ordinary majordomo mailing lists. You can subscribe by
sending a mail to: sending a mail to:
<UL>
* majordomo@listserv.direct.net <LI> <a
href="mailto:majordomo@listserv.direct.net">majordomo@listserv.direct.net</a>
OpenLink ODBC is very popular. You can get it from </UL>
http://www.openlinksw.com/postgres.html. It works with our standard ODBC <P>
client software so you'll have Postgres ODBC available on every client OpenLink ODBC is very popular. You can get it from <a
platform we support (Win, Mac, Unix, VMS). href="http://www.openlinksw.com/">
http://www.openlinksw.com/postgres.html</a>. It works with our standard
ODBC client software so you'll have Postgres ODBC available on every
client platform we support (Win, Mac, Unix, VMS).
<P>
We will probably be selling this product to people who need We will probably be selling this product to people who need
commercial-quality support, but a freeware version will always be available. commercial-quality support, but a freeware version will always be
Questions to postgres95@openlink.co.uk. available. Questions to <a
href="mailto:postgres95@openlink.co.uk">postgres95@openlink.co.uk</a>.
1.12) What tools are available for hooking postgres to Web pages? <P>
<H3><a name="1.12">1.12</a>) What tools are available for hooking
postgres to Web pages?</H3>
<P>
A nice introduction to Database-backed Web pages can be seen at: A nice introduction to Database-backed Web pages can be seen at:
http://www.webtools.com <a href="http://www.webtools.com">http://www.webtools.com</a>
<P>
For web integration, PHP is an excellent interface. The URL for that is For web integration, PHP is an excellent interface. The URL for that
http://php.iquest.net is <a href="http://www.php.net">http://www.php.net</a>
<P>
PHP is great for simple stuff, but for more complex stuff, some still use PHP is great for simple stuff, but for more complex stuff, some still
the perl interface and CGI.pm. use the perl interface and CGI.pm.
<P>
An WWW gatway based on WDB using perl can be downloaded from: An WWW gatway based on WDB using perl can be downloaded from:
<UL>
* http://www.eol.ists.ca/~dunlop/wdb -p95 <LI>
<a
1.13) Does PostgreSQL have a graphical user interface? A report generator? A href="http://www.eol.ists.ca/~dunlop/wdb-p95">http://www.eol.ists.ca/~dunlop/wd
embedded query language interface? b
-p95</a>
No. No. No. Not in the official distribution at least. Some users have </UL>
reported some success at using 'pgbrowse' and 'onyx' as frontends to <H3><a name="1.13">1.13</a>) Does PostgreSQL have a graphical user interface
PostgreSQL. Several contributions are working on tk based frontend tools. ?
Ask on the mailing list. A report generator? A embedded query language interface?</H3>
<P>
1.14) What is a good book to learn SQL? We have a nice graphical user interface called pgaccess, which is
shipped as part of the distribtion. Pgaccess also has a report
Many of our users like The Practical SQL Handbook, Bowman et al, Addison generator.
Wesley. <P>
We also have ecpg, which is an embedded SQL query language interface for
------------------------------------------------------------------------ C. This is also included.
<P>
Section 2: Installation Questions <H3><a name="1.14">1.14</a>) What is a good book to learn SQL?</H3>
<P>
2.1) initdb doesn't run Many of our users like <I>The Practical SQL Handbook</I>,
Bowman et al, Addison Wesley.
* check to see that you have the proper paths set <P>
* check that the 'postgres' user owns all the right files
* ensure that there are files in $PGDATA/files, and that they are <HR>
non-empty. If they aren't, then "gmake install" failed for some reason <H2> Section 2: Installation Questions
</H2>
2.2) when I start up the postmaster, I get "FindBackend: could not find a <P>
backend to execute..." "postmaster: could not find backend to execute..." <H3><a name="2.1">2.1</a>) initdb doesn't run</H3>
<P>
You probably do not have the right path set up. The 'postgres' executable <UL>
needs to be in your path. <LI> check to see that you have the proper paths set
<LI> check that the 'postgres' user owns all the right files
2.3) The system seems to be confused about commas, decimal points, and date <LI> ensure that there are files in $PGDATA/files, and that they
formats. are non-empty. If they aren't, then "gmake install" failed for
some reason
Check your locale configuration. PostgreSQL uses the locale settings of the </UL>
user that ran the postmaster process. Set those accordingly for your <P>
operating environment. <H3><a name="2.2">2.2</a>) when I start up the postmaster, I get
"FindBackend: could not find a backend to execute..."
2.4) How do I install PostgreSQL somewhere other than /usr/local/pgsql? "postmaster: could not find backend to execute..."</H3>
<P>
You probably do not have the right path set up. The 'postgres'
executable needs to be in your path.
<P>
<H3><a name="2.3">2.3</a>) The system seems to be confused about commas,
decimal points, and date formats.</H3>
<P>
Check your locale configuration. PostgreSQL uses the locale settings of
the user that ran the postmaster process. Set those accordingly for
your operating environment.
<P>
<H3><a name="2.4">2.4</a>) How do I install PostgreSQL somewhere other tha
n
/usr/local/pgsql?</H3>
<P>
You need to edit Makefile.global and change POSTGRESDIR accordingly, or You need to edit Makefile.global and change POSTGRESDIR accordingly, or
create a Makefile.custom and define POSTGRESDIR there. create a Makefile.custom and define POSTGRESDIR there.
<P>
2.5) When I run postmaster, I get a Bad System Call core dumped message. <H3><a name="2.5">2.5</a>) When I run postmaster, I get a Bad System
Call core dumped message.</H3>
<P>
It could be a variety of problems, but first check to see that you have It could be a variety of problems, but first check to see that you have
system V extensions installed on your kernel. PostgreSQL requires kernel system V extensions installed on your kernel. PostgreSQL requires kernel
support for shared memory. support for shared memory.
<P>
2.6) When I try to start the postmaster, I get IpcMemoryCreate errors. <H3><a name="2.6">2.6</a>) When I try to start the postmaster, I get
IpcMemoryCreate errors.</H3>
You either do not have shared memory configured properly in kernel or you <P>
need to enlarge the shared memory available in the kernel. The exact amount You either do not have shared memory configured properly in kernel or
you need depends on your architecture and how many buffers you configure you need to enlarge the shared memory available in the kernel. The
postmaster to run with. For most systems, with default buffer sizes, you exact amount you need depends on your architecture and how many buffers
need a minimum of ~760K. you configure postmaster to run with. For most systems, with default
buffer sizes, you need a minimum of ~760K.
2.7) I have changed a source file, but a recompile does not see the change? <P>
<H3><a name="2.7">2.7</a>) I have changed a source file, but a
recompile does not see the change?</H3>
<P>
The Makefiles do not have the proper dependencies for include files. You The Makefiles do not have the proper dependencies for include files. You
have to do a 'make clean' and then another 'make'. have to do a 'make clean' and then another 'make'.
<P>
2.8) How do I prevent other hosts from accessing my PostgreSQL backend? <H3><a name="2.8">2.8</a>) How do I prevent other hosts from accessing my
PostgreSQL backend?</H3>
Use host-based authentication by modifying the file $PGDATA/pg_hba <P>
By default, PostgreSQL only allows connections from the local machine
using unix domain. You must add the -i flag to the postmaster, and
enable host-based authentication by modifying the file $PGDATA/pg_hba
accordingly. accordingly.
<P>
2.9) I can't access the database as the 'root' user. <H3><a name="2.9">2.9</a>) I can't access the database as the 'root'
user.</H3>
<P>
You should not create database users with user id 0(root). They will be You should not create database users with user id 0(root). They will be
unable to access the database. This is a security precaution because of the unable to access the database. This is a security precaution because
ability of any user to dynamically link object modules into the database of the ability of any user to dynamically link object modules into the
engine. database engine.
<P>
2.10) All my servers crash under concurrent table access. Why? <H3><a name="2.10">2.10</a>) All my servers crash under concurrent table
access. Why?</H3>
<P>
This problem can be caused by a kernel that is not configured to support This problem can be caused by a kernel that is not configured to support
semaphores. semaphores.
<P>
2.11) How do I tune the database engine for better performance? <H3><a name="2.11">2.11</a>) How do I tune the database engine for
better performance?</H3>
There are two things that can be done. You can use Openlink's option to <P>
disable fsync() by starting the postmaster with a '-o -F' option. This will There are two things that can be done. You can disable fsync() by
prevent fsync()'s from flushing to disk after every transaction. starting the postmaster with a '-o -F' option. This
will prevent fsync()'s from flushing to disk after every transaction.
You can also use the postmaster -B option to increase the number of shared <P>
memory buffers shared among the backend processes. If you make this You can also use the postmaster -B option to increase the number of
parameter too high, the process will not start or crash unexpectedly. Each shared memory buffers shared among the backend processes. If you make
buffer is 8K and the defualt is 64 buffers. this parameter too high, the process will not start or crash
unexpectedly. Each buffer is 8K and the defualt is 64 buffers.
You can also use the postgres -S option to increase the maximum amount of <P>
memory used by each backend process for temporary sorts. Each buffer is 1K You can also use the postgres -S option to increase the maximum
and the defualt is 512 buffers. amount of memory used by each backend process for temporary sorts.
Each buffer is 1K and the defualt is 512 buffers.
2.12) What debugging features are available in PostgreSQL? <P>
<H3><a name="2.12">2.12</a>) What debugging features are available in
PostgreSQL has several features that report status information that can be PostgreSQL?</H3>
valuable for debugging purposes. <P>
PostgreSQL has several features that report status information that can
First, by running configure with the -enable-cassert option, many assert()'s be valuable for debugging purposes.
monitor the progress of the backend and halt the program when something <P>
unexpected occurs. First, by running configure with the -enable-cassert option,
many assert()'s monitor the progress of the backend and halt the
Both postmaster and postgres have several debug options available. First, program when something unexpected occurs.
whenever you start the postmaster, make sure you send the standard output <P>
and error to a log file, like: Both postmaster and postgres have several debug options available.
First, whenever you start the postmaster, make sure you send the
standard output and error to a log file, like:
<PRE>
<KBD>
cd /usr/local/pgsql cd /usr/local/pgsql
./bin/postmaster >server.log 2>&1 & ./bin/postmaster &gt;server.log 2&gt;&1 &
</KBD>
This will put a server.log file in the top-level PostgreSQL directory. This </PRE>
file can contain useful information about problems or errors encountered by <P>
the server. Postmaster has a -d option that allows even more detailed This will put a server.log file in the top-level PostgreSQL directory.
information to be reported. The -d option takes a number 1-3 that specifies This file can contain useful information about problems or errors
the debug level. Be warned that a debug level of 3 generates large log encountered by the server. Postmaster has a -d option that allows even
files. more detailed information to be reported. The -d option takes a number
1-3 that specifies the debug level. Be warned that a debug level
of 3 generates large log files.
<P>
You can actuall run the postgres backend from the command line, and type You can actuall run the postgres backend from the command line, and type
your SQL statement directly. This is recommended ONLY for debugging your SQL statement directly. This is recommended ONLY for debugging
purposes. Note that a newline terminates the query, not a semicolon. If you purposes. Note that a newline terminates the query, not a semicolon. If
have compiled with debugging symbols, you can use a debugger to see what is you have compiled with debugging symbols, you can use a debugger
happening. Because the backend was not started from the postmaster, it is to see what is happening. Because the backend was not started from the
not running in an identical environment and locking/backend interaction postmaster, it is not running in an identical environment and
problems may not be duplicated. Some operating system can attach to a locking/backend interaction problems may not be duplicated. Some
running backend directly to diagnose problems. operating system can attach to a running backend directly to diagnose
problems.
The postgres program has a -s, -A, -t options that can be very usefull for <P>
debugging and performance measurements. The postgres program has a -s, -A, -t options that can be very usefull
for debugging and performance measurements.
<P>
You can also compile with profiling to see what functions are taking You can also compile with profiling to see what functions are taking
execution time. The backend profile files will be deposited in the execution time. The backend profile files will be deposited in the
pgsql/data/base/dbname directory. The client profile file will be put in the pgsql/data/base/dbname directory. The client profile file will be put
current directory. in the current directory.
<P>
The EXPLAIN command (see this FAQ) allows you to see how PostgreSQL is The EXPLAIN command (see this FAQ) allows you to see how PostgreSQL is
interpreting your query. interpreting your query.
<P>
2.13) How do I enable more than 32 concurrent backends? <H3><a name="2.13">2.13</a>) How do I enable more than 32 concurrent
backends?</H3>
Edit include/storage/sinvaladt.h, and change the value of MaxBackendId. In <P>
the future, we plan to make this a configurable prameter. Edit include/storage/sinvaladt.h, and change the value of MaxBackendId.
In the future, we plan to make this a configurable prameter.
------------------------------------------------------------------------ <P>
Section 3: PostgreSQL Features <HR>
<H2> Section 3: PostgreSQL Features
3.1) Does PostgreSQL support nested subqueries? </H2>
<P>
Subqueries are not implemented, but they can be simulated using sql <H3><a name="3.1">3.1</a>) Does PostgreSQL support nested subqueries?</H3>
functions. <P>
Yes.
3.2) I've having a lot of problems using rules. <P>
<H3><a name="3.2">3.2</a>) I've having a lot of problems using rules.</H3>
Currently, the rule system in PostgreSQL is mostly broken. It works enough <P>
to support the view mechanism, but that's about it. Use PostgreSQL rules at Currently, the rule system in PostgreSQL has some limitations. It works
your own peril. enough to support the view mechanism, but does not handle
Insert/Update/Delete well.
3.3) I can't seem to write into the middle of large objects reliably. <P>
<H3><a name="3.3">3.3</a>) I can't seem to write into the middle of large
The Inversion large object system in PostgreSQL is also mostly broken. It objects reliably.</H3>
works well enough for storing large wads of data and reading them back out, <P>
but the implementation has some underlying problems. Use PostgreSQL large The Inversion large object system now works perfectly. You should no
objects at your own peril. longer have problems with large objects.
<P>
3.4) How can I write client applications to PostgreSQL? <H3><a name="3.4">3.4</a>) How can I write client applications to PostgreS
QL?</H3>
PostgreSQL supports a C-callable library interface called libpq as well as <P>
many others. See the /src/interfaces directory. PostgreSQL supports a C-callable library interface called libpq as well
as many others. See the /src/interfaces directory.
Others have contributed a perl interface and a WWW gateway to PostgreSQL. <P>
See the PostgreSQL home pages for more details. Others have contributed a perl interface and a WWW gateway to
PostgreSQL. See the PostgreSQL home pages for more details.
3.5) How do I set up a pg_group? <P>
<H3><a name="3.5">3.5</a>) How do I set up a pg_group?</H3>
<P>
Currently, there is no easy interface to set up user groups. You have to Currently, there is no easy interface to set up user groups. You have to
explicitly insert/update the pg_group table. For example: explicitly insert/update the pg_group table. For example:
<PRE>
jolly=> insert into pg_group (groname, grosysid, grolist) <CODE>
jolly=> values ('posthackers', '1234', '{5443, 8261}'); jolly=&gt; insert into pg_group (groname, grosysid, grolist)
jolly=&gt; values ('posthackers', '1234', '{5443, 8261}');
INSERT 548224 INSERT 548224
jolly=> grant insert on foo to group posthackers; jolly=&gt; grant insert on foo to group posthackers;
CHANGE CHANGE
jolly=> jolly=&gt;
</CODE>
The fields in pg_group are: </PRE>
<P>
* groname: the group name. This a char16 and should be purely The fields in pg_group are:
alphanumeric. Do not include underscores or other punctuation. <UL>
* grosysid: the group id. This is an int4. This should be unique for each <LI> groname: the group name. This a char16 and should
group. be purely alphanumeric. Do not include underscores
* grolist: the list of pg_user id's that belong in the group. This is an or other punctuation.
int4[]. <LI> grosysid: the group id. This is an int4.
This should be unique for each group.
3.6) What is the exact difference between binary cursors and normal cursors? <LI> grolist: the list of pg_user id's that belong in the group.
This is an int4[].
See the declare manual page for a description. </UL>
<P>
3.7) What is a R-tree index and what is it used for? <H3><a name="3.6">3.6</a>) What is the exact difference between binary
cursors and normal cursors?</H3>
An r-tree index is used for indexing spatial data. A hash index can't handle <P>
range searches. A B-tree index only handles range searches in a single See the <I>declare</I> manual page for a description.
dimension. R-tree's can handle multi-dimensional data. For example, if a <P>
R-tree index can be built on an attribute of type 'point', the system can <H3><a name="3.7">3.7</a>) What is a R-tree index and what is it used for?
more efficient answer queries like select all points within a bounding </H3>
rectangle. <P>
An r-tree index is used for indexing spatial data. A hash index can't
handle range searches. A B-tree index only handles range searches in a
single dimension. R-tree's can handle multi-dimensional data. For
example, if a R-tree index can be built on an attribute of type 'point',
the system can more efficient answer queries like select all points
within a bounding rectangle.
<P>
The canonical paper that describes the original R-Tree design is: The canonical paper that describes the original R-Tree design is:
<P>
Guttman, A. "R-Trees: A Dynamic Index Structure for Spatial Searching." Proc Guttman, A. "R-Trees: A Dynamic Index Structure for Spatial Searching."
of the 1984 ACM SIGMOD Int'l Conf on Mgmt of Data, 45-57. Proc of the 1984 ACM SIGMOD Int'l Conf on Mgmt of Data, 45-57.
<P>
You can also find this paper in Stonebraker's "Readings in Database Systems" You can also find this paper in Stonebraker's "Readings in Database
Systems"
Builtin R-Trees can handle polygons and boxes. In theory, R-trees can be <P>
extended to handle higher number of dimensions. In practice, extending Builtin R-Trees can handle polygons and boxes. In theory, R-trees can
R-trees require a bit of work and we don't currently have any documentation be extended to handle higher number of dimensions. In practice,
on how to do it. extending R-trees require a bit of work and we don't currently have any
documentation on how to do it.
3.8) What is the maximum size for a tuple? <P>
<H3><a name="3.8">3.8</a>) What is the maximum size for a tuple?</H3>
Tuples are limited to 8K bytes. Taking into account system attributes and <P>
other overhead, one should stay well shy of 8,000 bytes to be on the safe Tuples are limited to 8K bytes. Taking into account system attributes
side. To use attributes larger than 8K, try using the large objects and other overhead, one should stay well shy of 8,000 bytes to be on the
interface. safe side. To use attributes larger than 8K, try using the large
objects interface.
Tuples do not cross 8k boundaries so a 5k tuple will require 8k of storage. <P>
Tuples do not cross 8k boundaries so a 5k tuple will require 8k of
3.9) I defined indices but my queries don't seem to make use of them. Why? storage.
<P>
PostgreSQL does not automatically maintain statistics. One has to make an <H3><a name="3.9">3.9</a>) I defined indices but my queries don't seem
explicit 'vacuum' call to update the statistics. After statistics are to make use of them. Why?</H3>
updated, the optimizer has a better shot at using indices. Note that the <P>
optimizer is limited and does not use indices in some circumstances (such as PostgreSQL does not automatically maintain statistics. One has to make
OR clauses). For column-specific optimization statistics, use 'vacuum an explicit 'vacuum' call to update the statistics. After statistics
analyze'. are updated, the optimizer has a better shot at using indices. Note
that the optimizer is limited and does not use indices in some
If the system still does not see the index, it is probably because you have circumstances (such as OR clauses). For column-specific optimization
created an index on a field with the improper *_ops type. For example, you statistics, use 'vacuum analyze'.
have created a CHAR(4) field, but have specified a char_ops index <P>
type_class. If the system still does not see the index, it is probably because you
have created an index on a field with the improper *_ops type. For
See the create_index manual page for information on what type classes are example, you have created a CHAR(4) field, but have specified a char_ops
available. It must match the field type. index type_class.
<P>
See the create_index manual page for information on what type classes
are available. It must match the field type.
<P>
Postgres does not warn the user when the improper index is created. Postgres does not warn the user when the improper index is created.
<P>
Indexes not used for ORDER BY operations. Indexes not used for ORDER BY operations.
<P>
3.10) How do I do regular expression searches? case-insensitive regexp <H3><a name="3.10">3.10</a>) How do I do regular expression searches?
searching? case-insensitive regexp searching?</H3>
<P>
See the pgbuiltin manual page. Search for regular expression. See the <I>pgbuiltin</I> manual page. Search for <I>regular expression.</I>
<P>
3.11) I experienced a server crash during a vacuum. How do I remove the lock <H3><a name="3.11">3.11</a>) I experienced a server crash during a
file? vacuum. How do I remove the lock file?</H3>
<P>
See the vacuum manual page. See the <I>vacuum</I> manual page.
<P>
3.12) What is the difference between the various character types? <H3><a name="3.12">3.12</a>) What is the difference between the various
character types?</H3>
<PRE>
Type Internal Name Notes Type Internal Name Notes
-------------------------------------------------- --------------------------------------------------
CHAR char 1 character } CHAR char 1 character }
...@@ -593,180 +723,185 @@ CHAR(#) bpchar blank padded to the specified fixed length ...@@ -593,180 +723,185 @@ CHAR(#) bpchar blank padded to the specified fixed length
VARCHAR(#) varchar size specifies maximum length, no padding VARCHAR(#) varchar size specifies maximum length, no padding
TEXT text length limited only by maximum tuple length TEXT text length limited only by maximum tuple length
BYTEA bytea variable-length array of bytes BYTEA bytea variable-length array of bytes
</PRE>
<P>
You need to use the internal name when doing internal operations. You need to use the internal name when doing internal operations.
<P>
The last four types above are "varlena" types (i.e. the first four bytes are The last four types above are "varlena" types (i.e. the first four bytes
the length, followed by the data). CHAR(#) allocates the maximum number of are the length, followed by the data). CHAR(#) allocates the maximum
bytes no matter how much data is stored in the field. TEXT, VARCHAR(#), and number of bytes no matter how much data is stored in the field.
BYTEA all have variable length on the disk, and because of this, there is a TEXT, VARCHAR(#), and BYTEA all have variable length on the disk, and
small performance penalty for using them. Specifically, the penalty is for because of this, there is a small performance penalty for using them.
access to any columns after the first column of this type. Specifically, the penalty is for access to any columns after the first
column of this type.
3.13) In a query, how do I detect if a field is NULL? <P>
<H3><a name="3.13">3.13</a>) In a query, how do I detect if a field is NULL?
</H3>
<P>
You test the column with IS NULL and IS NOT NULL. You test the column with IS NULL and IS NOT NULL.
<P>
3.14) How do I see how the query optimizer is evaluating my query? <H3><a name="3.14">3.14</a>) How do I see how the query optimizer is
evaluating my query?</H3>
See the explain manual page. <P>
See the <I>explain</I> manual page.
3.15) How do I create a serial field? <P>
<H3><a name="3.15">3.15</a>) How do I create a serial field?</H3>
Postgres does not allow the user to specifiy a user column as type SERIAL. <P>
Instead, you can use each row's oid field as a unique value. However, if you Postgres does not allow the user to specifiy a user column as type
need to dump and reload the database, you need to use pgdump's -o option or SERIAL. Instead, you can use each row's oid field as a unique value.
COPY's WITH OIDS option to preserver the oids. However, if you need to dump and reload the database, you need to use
pgdump's -o option or COPY's WITH OIDS option to preserver the oids.
<P>
We also have a SEQUENCE function that is similar to SERIAL. See the We also have a SEQUENCE function that is similar to SERIAL. See the
create_sequence manual page. create_sequence manual page.
<P>
Another valid way of doing this is to create a function: Another valid way of doing this is to create a function:
<PRE>
<CODE>
create table my_oids (f1 int4); create table my_oids (f1 int4);
insert into my_oids values (1); insert into my_oids values (1);
create function new_oid () returns int4 as create function new_oid () returns int4 as
'update my_oids set f1 = f1 + 1; select f1 from my_oids; ' 'update my_oids set f1 = f1 + 1; select f1 from my_oids; '
language 'sql'; language 'sql';
</CODE>
</PRE>
<P>
then: then:
<PRE>
<CODE>
create table my_stuff (my_key int4, value text); create table my_stuff (my_key int4, value text);
insert into my_stuff values (new_oid(), 'hello'); insert into my_stuff values (new_oid(), 'hello');
</CODE>
However, keep in mind there is a race condition here where one server could </PRE>
do the update, then another one do an update, and they both could select the <P>
same new id. This statement should be performed within a transaction. However, keep in mind there is a race condition here where one server
could do the update, then another one do an update, and they both could
Yet another way is to use general trigger function autoinc() from select the same new id. This statement should be performed within a
contrib/spi/autoinc.c. transaction.
<P>
3.16) What are the pg_psort.XXX files in my database directory? Yet another way is to use general trigger function autoinc()
from contrib/spi/autoinc.c.
They are temporary sort files generated by the query executor. For example, <P>
if a sort needs to be done to satisfy an ORDER BY, some temp files are <H3><a name="3.16">3.16</a>) What are the pg_psort.XXX files in my database
generated as a result of the sort. directory?</H3>
<P>
They are temporary sort files generated by the query executor.
For example, if a sort needs to be done to satisfy an ORDER BY,
some temp files are generated as a result of the sort.
<P>
If you have no transactions or sorts running at the time, it is safe to If you have no transactions or sorts running at the time, it is safe to
delete the pg_psort.XXX files. delete the pg_psort.XXX files.
<P>
3.17) Why can't I connect to my database from another machine? <H3><a name="3.17">3.17</a>) Why can't I connect to my database from
another machine?</H3>
The default configuration allows only connections from tcp/ip host <P>
localhost. You need to add a host entry to the file pgsql/data/pg_hba. See The default configuration allows only unix domain socket connections
the hba_conf manual page. from the local machine. To enable TCP/IP connections, use the
postmaster -i option You need to add a host entry to the file
3.18) How do I find out what indexes or operations are defined in the pgsql/data/pg_hba. See the <I>hba_conf</I> manual page.
database? <P>
<H3><a name="3.18">3.18</a>) How do I find out what indexes or
Run the file pgsql/src/tutorial/syscat.source. It illustrates many of the operations are defined in the database?</H3>
'select's needed to get information out of the database system tables. <P>
psql has a variety of backslash commands to show such information. Use
3.19) What is the time-warp feature and how does it relate to vacuum? \? to see them.
<P>
PostgreSQL handles data changes differently than most database systems. When Also try the file pgsql/src/tutorial/syscat.source. It illustrates many of
a row is changed in a table, the original row is marked with the time it was the 'select's needed to get information out of the database system
changed, and a new row is created with the current data. By default, only tables.
current rows are used in a table. If you specify a date/time after the table <P>
name in a FROM clause, you can access the data that was current at that <H3><a name="3.19">3.19</a>) What is the time-warp feature and how does
time, i.e. it relate to vacuum?</H3>
<P>
SELECT * PostgreSQL no longer supports this feature. All support code has been
FROM employees ['July 24, 1996 09:00:00'] removed. This was done to improve performance and reduce disk storage
overhead.
displays employee rows in the table at the specified time. You can specify <P>
intervals like [date,date], [date,], [,date], or [,]. This last option <H3><a name="3.20">3.20</a>) What is an oid? What is a tid?</H3>
accesses all rows that ever existed. <P>
Oids are Postgres's answer to unique row ids or serial columns. Every
INSERTed rows get a timestamp too, so rows that were not in the table at the row that is created in Postgres gets a unique oid. All oids generated
desired time will not appear. by initdb are less than 16384 (from backend/access/transam.h). All
post-initdb (user-created) oids are equal or greater that this. All
Vacuum removes rows that are no longer current. This time-warp feature is these oids are unique not only within a table, or database, but unique
used by the engine for rollback and crash recovery. Expiration times can be within the entire postgres installation.
set with purge. <P>
Postgres uses oids in its internal system tables to link rows in
In 6.0, once a table is vacuumed, the creation time of a row may be separate tables. These oids can be used to identify specific user rows
incorrect, causing time-traval to fail. and used in joins. It is recommended you use column type oid to store
oid values. See the sql(l) manual page to see the other internal
The time-travel feature will be removed in 6.3. columns. You can create an index on the oid field for faster access.
<P>
3.20) What is an oid? What is a tid?
Oids are Postgres's answer to unique row ids or serial columns. Every row
that is created in Postgres gets a unique oid. All oids generated by initdb
are less than 16384 (from backend/access/transam.h). All post-initdb
(user-created) oids are equal or greater that this. All these oids are
unique not only within a table, or database, but unique within the entire
postgres installation.
Postgres uses oids in its internal system tables to link rows in separate
tables. These oids can be used to identify specific user rows and used in
joins. It is recommended you use column type oid to store oid values. See
the sql(l) manual page to see the other internal columns. You can create an
index on the oid field for faster access.
Tids are used to indentify specific physical rows with block and offset Tids are used to indentify specific physical rows with block and offset
values. Tids change after rows are modified or reloaded. They are used by values. Tids change after rows are modified or reloaded. They are used
index entries to point to physical rows. They can not be accessed through by index entries to point to physical rows. They can not be accessed
sql. through sql.
<P>
3.21) What is the meaning of some of the terms used in Postgres? <H3><a name="3.21">3.21</a>) What is the meaning of some of the terms
used in Postgres?</H3>
<P>
Some of the source code and older documentation use terms that have more Some of the source code and older documentation use terms that have more
common usage. Here are some: common usage. Here are some:
<UL>
* row, record, tuple <LI> row, record, tuple
* attribute, field, column <LI> attribute, field, column
* table, class <LI> table, class
* retrieve, select <LI> retrieve, select
* replace, update <LI> replace, update
* append, insert <LI> append, insert
* oid, serial value <LI> oid, serial value
* portal, cursor <LI> portal, cursor
* range variable, table name, table alias <LI> range variable, table name, table alias
</UL>
<P>
Please let me know if you think of any more. Please let me know if you think of any more.
<P>
3.22) What is Genetic Query Optimization? <H3><a name="3.22">3.22</a>) What is Genetic Query Optimization?</H3>
<P>
The GEQO module in PostgreSQL is intended to solve the query optimization The GEQO module in PostgreSQL is intended to solve the query
problem of joining many tables by means of a Genetic Algorithm (GA). It optimization problem of joining many tables by means of a Genetic
allows the handling of large join queries through non-exhaustive search. Algorithm (GA). It allows the handling of large join queries through
non-exhaustive search.
For further information see README.GEQO <utesch@aut.tu-freiberg.de>. <P>
For further information see README.GEQO &lt;utesch@aut.tu-freiberg.de&gt;.
3.23) How do you remove a column from a table? <P>
<H3><a name="3.23">3.23</a>) How do you remove a column from a table?</H3>
We do not support ALTER TABLE DROP COLUMN, but do this: We do not support ALTER TABLE DROP COLUMN, but do this:
<PRE>
<CODE>
SELECT ... -- select all columns but the one you want to remove SELECT ... -- select all columns but the one you want to remove
INTO TABLE new_table INTO TABLE new_table
FROM old_table; FROM old_table;
DROP TABLE old_table; DROP TABLE old_table;
ALTER TABLE new_table RENAME TO old_table; ALTER TABLE new_table RENAME TO old_table;
</CODE>
3.24) How do SELECT only the first few rows of a query? </PRE>
<P>
See the fetch manual page. <H3><a name="3.24">3.24</a>) How do SELECT only the first few rows of
a query?</H3>
This only prevents all row results from being transfered to the client. The <P>
entire query must be evaluated, even if you only want just first few rows. See the <I>fetch</I> manual page.
Consider a query that has and ORDER BY. There is no way to return any rows <P>
until the entire query is evaluated and sorted. This only prevents all row results from being transfered to the client.
The entire query must be evaluated, even if you only want just first few
3.25) Why can't I create a column named "time"? rows.
Consider a query that has and ORDER BY. There is no way to return any
rows until the entire query is evaluated and sorted.
<P>
<H3><a name="3.25">3.25</a>) Why can't I create a column named
"time"?<BR></H3>
<P>
6.2.1 has added some new restricted keywords as we make PostgreSQL more 6.2.1 has added some new restricted keywords as we make PostgreSQL more
ANSI-92 compilant. The next release will have this restriction removed. ANSI-92 compilant. The next release will have this restriction removed.
There is a patch on ftp.postgresql.org that will allow this feature now. There is a patch on ftp.postgresql.org that will allow this feature now.
<P>
3.26)How much database disk space is required to store data from a typical <H3><a name="3.26">3.26</a>)How much database disk space is required
flat file? to store data from a typical flat file?<BR></H3>
<P>
Consider a file with 300,000 lines with two integers on each line. The flat Consider a file with 300,000 lines with two integers on each line.
file is 2.4MB. The size of the PostgreSQL database file containing this data The flat file is 2.4MB. The size of the PostgreSQL database file
can be estimated: containing this data can be estimated:
<PRE>
40 bytes + each row header (approximate) 40 bytes + each row header (approximate)
8 bytes + two int fields @ 4 bytes each 8 bytes + two int fields @ 4 bytes each
4 bytes + pointer on page to tuple 4 bytes + pointer on page to tuple
...@@ -784,54 +919,67 @@ The data page size in PostgreSQL is 8192(8k) bytes, so: ...@@ -784,54 +919,67 @@ The data page size in PostgreSQL is 8192(8k) bytes, so:
157 rows per page 157 rows per page
1911 database pages * 8192 bytes per page = 15,654,912 or 15.5MB 1911 database pages * 8192 bytes per page = 15,654,912 or 15.5MB
<P>
Indexes do not contain as much overhead, but do contain the data that Indexes do not contain as much overhead, but do contain the data that
is being indexed, so they can be large also. is being indexed, so they can be large also.
</PRE>
------------------------------------------------------------------------ <P>
<HR>
Section 4: Extending PostgreSQL <H2> Section 4: Extending PostgreSQL
</H2>
4.1) I wrote a user-defined function and when I run it in psql, it dumps <P>
core. <H3><a name="4.1">4.1</a>) I wrote a user-defined function and when I run
it
in psql, it dumps core.</H3>
<P>
The problem could be a number of things. Try testing your user-defined The problem could be a number of things. Try testing your user-defined
function in a stand alone test program first. Also, make sure you are not function in a stand alone test program first. Also, make sure you are
sending elog NOTICES when the front-end is expecting data, such as during a not sending elog NOTICES when the front-end is expecting data, such as
type_in() or type_out() functions during a type_in() or type_out() functions
<P>
4.2) I get messages of the type NOTICE:PortalHeapMemoryFree: 0x402251d0 not <H3><a name="4.2">4.2</a>) I get messages of the type
in alloc set! NOTICE:PortalHeapMemoryFree: 0x402251d0 not in alloc set!</H3>
<P>
You are pfree'ing something that was not palloc'ed. When writing You are pfree'ing something that was not palloc'ed. When writing
user-defined functions, do not include the file "libpq-fe.h". Doing so will user-defined functions, do not include the file "libpq-fe.h". Doing so
cause your palloc to be a malloc instead of a free. Then, when the backend will cause your palloc to be a malloc instead of a free. Then, when the
pfrees the storage, you get the notice message. backend pfrees the storage, you get the notice message.
<P>
4.3) I've written some nifty new types and functions for PostgreSQL. <H3><a name="4.3">4.3</a>) I've written some nifty new types and functions
for
PostgreSQL.</H3>
<P>
Please share them with other PostgreSQL users. Send your extensions to Please share them with other PostgreSQL users. Send your extensions to
mailing list, and they will eventually end up in the contrib/ subdirectory. mailing list, and they will eventually end up in the contrib/
subdirectory.
4.4) How do I write a C function to return a tuple? <P>
<H3><a name="4.4">4.4</a>) How do I write a C function to return a tuple?<
This requires extreme wizardry, so extreme that the authors have not ever /H3>
tried it, though in principle it can be done. The short answer is ... you <P>
can't. This capability is forthcoming in the future. This requires extreme wizardry, so extreme that the authors have not
ever tried it, though in principle it can be done. The short answer is
------------------------------------------------------------------------ ... you can't. This capability is forthcoming in the future.
<P>
Section 5: Bugs
<HR>
5.1) How do I make a bug report? <H2> Section 5: Bugs
</H2>
Check the current FAQ at http://postgreSQL.org <P>
<H3><a name="5.1">5.1</a>) How do I make a bug report?</H3>
Also check out our ftp site ftp://ftp.postgreSQL.org/pub to see if there is <P>
a more recent PostgreSQL version. Check the current FAQ at <a
href="http://postgreSQL.org">http://postgreSQL.org</a>
<P>
Also check out our ftp site <a
href="ftp://ftp.postgreSQL.org/pub">ftp://ftp.postgreSQL.org/pub</a> to
see if there is a more recent PostgreSQL version.
<P>
You can also fill out the "bug-template" file and send it to: You can also fill out the "bug-template" file and send it to:
<UL>
* bugs@postgreSQL.org <LI> <a href="mailto:bugs@postgreSQL.org">bugs@postgreSQL.org</a>
</UL>
<P>
This is the address of the developers mailing list. This is the address of the developers mailing list.
</BODY>
</HTML>
doc/TODO
View file @ f0410b1e
TODO list for PostgreSQL TODO list for PostgreSQL
======================== ========================
Last updated: Sun Feb 1 15:08:57 EST 1998 Last updated: Fri Feb 27 13:32:53 EST 1998
Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us) Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
...@@ -30,6 +30,7 @@ Developers who have claimed items are: ...@@ -30,6 +30,7 @@ Developers who have claimed items are:
* Kurt is "Kurt J. Lidl" <lidl@va.pubnix.com> * Kurt is "Kurt J. Lidl" <lidl@va.pubnix.com>
* Marc is Marc Fournier <scrappy@hub.org> * Marc is Marc Fournier <scrappy@hub.org>
* Martin is Martin S. Utesch <utesch@aut.tu-freiberg.de> * Martin is Martin S. Utesch <utesch@aut.tu-freiberg.de>
* Michael is Michael Meskes <meskes@topsystem.de>
* Oleg is Oleg Bartunov <oleg@sai.msu.su> * Oleg is Oleg Bartunov <oleg@sai.msu.su>
* Paul is Paul M. Aoki <aoki@CS.Berkeley.EDU> * Paul is Paul M. Aoki <aoki@CS.Berkeley.EDU>
* Patrick is Patrick van Kleef <pvk@pobox.com> * Patrick is Patrick van Kleef <pvk@pobox.com>
...@@ -45,10 +46,10 @@ Developers who have claimed items are: ...@@ -45,10 +46,10 @@ Developers who have claimed items are:
* Vadim is "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su> * Vadim is "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>
* Vivek is Vivek Khera <khera@kci.kciLink.com> * Vivek is Vivek Khera <khera@kci.kciLink.com>
Additional; 6.3 developers include: Additional 6.3 developers include:
--------------------------------- ---------------------------------
* Billy is Billy G. Allie <Bill.Allie@mug.org> * Billy is Billy G. Allie <Bill.Allie@mug.org>
* Brook is Brook Milligan * Brook is Brook Milligan <brook@trillium.NMSU.Edu>
* James is James Hughes <jamesh@interpath.com> * James is James Hughes <jamesh@interpath.com>
* Jeroen is Jeroen van Vianen <jeroenv@design.nl> * Jeroen is Jeroen van Vianen <jeroenv@design.nl>
* Matt is Matt Maycock <maycock@intelliquest.com> * Matt is Matt Maycock <maycock@intelliquest.com>
...@@ -63,7 +64,8 @@ RELIABILITY ...@@ -63,7 +64,8 @@ RELIABILITY
* Overhaul bufmgr/lockmgr/transaction manager * Overhaul bufmgr/lockmgr/transaction manager
* -Fix CLUSTER * -Fix CLUSTER
* Remove EXTEND? * Remove EXTEND?
* -Aggregates on VIEW always returns zero (maybe because there is no oid for views?) * -Aggregates on VIEW always returns zero (maybe because there is no oid for vi
ews?)
* CREATE VIEW requires super-user priviledge * CREATE VIEW requires super-user priviledge
* Can lo_export()/lo_import() read/write anywhere, causing a security problem? * Can lo_export()/lo_import() read/write anywhere, causing a security problem?
* Tables that start with xinv confused to be large objects * Tables that start with xinv confused to be large objects
...@@ -79,9 +81,10 @@ RELIABILITY ...@@ -79,9 +81,10 @@ RELIABILITY
* UPDATE table SET table.value = 3 fails * UPDATE table SET table.value = 3 fails
* -UPDATE key_table SET keyval=count(reftab.num) fails * -UPDATE key_table SET keyval=count(reftab.num) fails
* -INSERT INTO ... SELECT DISTINCT ... does not accept DISTINCT * -INSERT INTO ... SELECT DISTINCT ... does not accept DISTINCT
* -INSERT INTO table SELECT id, count(*) FROM table2 GROUP BY id generates error
* Make pg_dump preserve inheritance column order, do non-inherits first * Make pg_dump preserve inheritance column order, do non-inherits first
* User who can create databases can modify pg_database table * User who can create databases can modify pg_database table
* optimizer memory exhaustion with many OR's
* elog() does not free all its memory(Jan)
ENHANCEMENTS ENHANCEMENTS
------------ ------------
...@@ -145,7 +148,8 @@ ENHANCEMENTS ...@@ -145,7 +148,8 @@ ENHANCEMENTS
* add UNIQUE capability to non-btree indexes * add UNIQUE capability to non-btree indexes
* make number of backends a config parameter, storage/sinvaladt.h:MaxBackendId * make number of backends a config parameter, storage/sinvaladt.h:MaxBackendId
* certain indexes will not shrink, i.e. oid indexes with many inserts * certain indexes will not shrink, i.e. oid indexes with many inserts
* make NULL's come out at the beginning or end depending on the ORDER BY direction * make NULL's come out at the beginning or end depending on the ORDER BY direct
ion
* change the library/backend interface to use network byte order * change the library/backend interface to use network byte order
* -allow unix domain sockets for local connections for performance and security * -allow unix domain sockets for local connections for performance and security
* -Add PAGER for psql's \dt, \d, \z tablename * -Add PAGER for psql's \dt, \d, \z tablename
...@@ -162,13 +166,24 @@ ENHANCEMENTS ...@@ -162,13 +166,24 @@ ENHANCEMENTS
* Fix compile and security of Kerberos/GSSAPI code * Fix compile and security of Kerberos/GSSAPI code
* Allow psql to print nulls as distinct from ""(?) * Allow psql to print nulls as distinct from ""(?)
* Allow variable casts with BETWEEN 'today'::asbtime AND 'today'::abstime * Allow variable casts with BETWEEN 'today'::asbtime AND 'today'::abstime
* Allow VIEW permissions to be set separately from the underlying tables * -Allow VIEW permissions to be set separately from the underlying tables
* Allow INSERT INTO ... SELECT ... FROM view to work
* Allow text, char(), and varchar() overhead to be only 2 bytes, not 4 bytes * Allow text, char(), and varchar() overhead to be only 2 bytes, not 4 bytes
* Make VACUUM on database not lock pg_class
* Make VACUUM ANALYZE only use a readlock
* Allow cursors to be DECLAREd/OPENed/CLOSEed outside transactions
* Allow installation data block size and max tuple size configuration(Darren)
* Allow views on a UNION
* Allow views of aggregate columns
* Allow variable block sizes(Darren)
* System tables are now more update-able from SQL(Jan)
* New pg_shadow file, pg_user is now a view of pg_shadow(Jan)
PERFORMANCE PERFORMANCE
----------- -----------
* Use indexes in ORDER BY, min(), max() * Use indexes in ORDER BY, min(), max()(Costin Oproiu)
* -Allow LIKE/wildcard matches to use indexes if the wildcard character is not first * -Allow LIKE/wildcard matches to use indexes if the wildcard character is not
first
* Optimizing disjunctive queries * Optimizing disjunctive queries
* Fix bushy-plans (Martin) * Fix bushy-plans (Martin)
* Other optimizer bugs * Other optimizer bugs
...@@ -181,6 +196,8 @@ PERFORMANCE ...@@ -181,6 +196,8 @@ PERFORMANCE
* update pg_statistic table to remove operator column * update pg_statistic table to remove operator column
* make index creation use psort code, because it is now faster(Vadim) * make index creation use psort code, because it is now faster(Vadim)
* remove fork()/exec() of backend and make it just fork() * remove fork()/exec() of backend and make it just fork()
* Improve vacuum locking issues
* Add base table name to \d index
DOCUMENTATION DOCUMENTATION
------------- -------------
...@@ -195,33 +212,6 @@ DOCUMENTATION ...@@ -195,33 +212,6 @@ DOCUMENTATION
CHANGES IN THE 6.3 RELEASE CHANGES IN THE 6.3 RELEASE
-------------------------- --------------------------
Developers who have claimed items are:
-------------------------------------
* Billy is Billy G. Allie <Bill.Allie@mug.org>
* Brook is Brook Milligan
* Bruce is Bruce Momjian <maillist@candle.pha.pa.us>
* D'Arcy is D'Arcy J.M. Cain <darcy@druid.net>
* Dan is Dan McGuirk <mcguirk@indirect.com>
* Darren is Darren King <darrenk@insightdist.com>
* Goran is Goran Thyni <goran@bildbasen.se>
* Henry is Henry B. Hotz <hotz@jpl.nasa.gov>
* James is James Hughes <jamesh@interpath.com>
* Jan is Jan Wieck <wieck@sapserv.debis.de>
* Jeroen is Jeroen van Vianen <jeroenv@design.nl>
* Marc is Marc Fournier <scrappy@hub.org>
* Martin is Martin S. Utesch <utesch@aut.tu-freiberg.de>
* Matt is Matt Maycock <maycock@intelliquest.com>
* Peter is Peter T Mount <psqlhack@maidast.demon.co.uk>
* Phil is Phil Thompson <phil@river-bank.demon.co.uk>
* Ryan is Ryan Kirkpatrick <rkirkpat@nag.cs.colorado.edu>
* Tatsuo is Tatsuo Ishii <t-ishii@sra.co.jp>
* Thomas is Thomas Lockhart <lockhart@alumni.caltech.edu>
* TomH is Tom I Helbekkmo <tih@Hamartun.Priv.NO>
* TomS is Tom Szybist
* Todd is Todd Brandys is <brandys@eng3.hep.uiuc.edu>
* Travis is Travis Melhiser <melhiser@viper.co.union.nc.us>
* Vadim is "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>
Bug Fixes Bug Fixes
--------- ---------
Fix binary cursors broken by MOVE implementation(Vadim) Fix binary cursors broken by MOVE implementation(Vadim)
...@@ -254,25 +244,28 @@ Generate elog(ERROR) on over-large integer(Bruce) ...@@ -254,25 +244,28 @@ Generate elog(ERROR) on over-large integer(Bruce)
Allow multiple-argument functions in constraint clauses(Thomas) Allow multiple-argument functions in constraint clauses(Thomas)
Check boolean input literals for 'true','false','yes','no','1','0' Check boolean input literals for 'true','false','yes','no','1','0'
and throw elog(ERROR) if unrecognized(Thomas) and throw elog(ERROR) if unrecognized(Thomas)
Major large objects fix
Enhancements Enhancements
------------ ------------
Subselects with EXISTS, IN, ALL, ANY keywords (Vadim, Bruce, Thomas)
New User Manual(Thomas, others)
Speedup by inlining some frequently-called functions
Real deadlock detection, no more timeouts(Bruce) Real deadlock detection, no more timeouts(Bruce)
<NOT DONE YET> Subselects with EXISTS, IN, ALL, ANY keywords (Vadim, Bruce, Thomas)
Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
CURRENT_USER(Thomas) CURRENT_USER(Thomas)
Speedup by inlining some frequently-called functions
Modify constraint syntax to be SQL92-compliant(Thomas) Modify constraint syntax to be SQL92-compliant(Thomas)
Implement SQL92 PRIMARY KEY and UNIQUE clauses using indices(Thomas) Implement SQL92 PRIMARY KEY and UNIQUE clauses using indices(Thomas)
Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas) Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
Allow NOT NULL UNIQUE constraint clause (each allowed separately before)(Thomas) Allow NOT NULL UNIQUE constraint clause (each allowed separately before)(Thomas
)
Allow Postgres-style casting ("::") of non-constants(Thomas) Allow Postgres-style casting ("::") of non-constants(Thomas)
Add support for SQL3 TRUE and FALSE boolean constants(Thomas) Add support for SQL3 TRUE and FALSE boolean constants(Thomas)
Support SQL92 syntax for IS TRUE/IS FALSE/IS NOT TRUE/IS NOT FALSE(Thomas) Support SQL92 syntax for IS TRUE/IS FALSE/IS NOT TRUE/IS NOT FALSE(Thomas)
Allow shorter strings for boolean literals (e.g. "t", "tr", "tru")(Thomas) Allow shorter strings for boolean literals (e.g. "t", "tr", "tru")(Thomas)
Allow SQL92 delimited identifiers(Thomas) Allow SQL92 delimited identifiers(Thomas)
Implement SQL92 binary and hexadecimal string decoding (b'10' and x'1F')(Thomas) Implement SQL92 binary and hexadecimal string decoding (b'10' and x'1F')(Thomas
)
Support SQL92 syntax for type coercion of literal strings Support SQL92 syntax for type coercion of literal strings
(e.g. "DATETIME 'now'")(Thomas) (e.g. "DATETIME 'now'")(Thomas)
Add conversions for int2, int4, and OID types to and from text(Thomas) Add conversions for int2, int4, and OID types to and from text(Thomas)
...@@ -294,7 +287,8 @@ Augment support for SQL92 SET TIME ZONE...(Thomas) ...@@ -294,7 +287,8 @@ Augment support for SQL92 SET TIME ZONE...(Thomas)
SET/SHOW/RESET TIME ZONE uses TZ backend environment variable(Thomas) SET/SHOW/RESET TIME ZONE uses TZ backend environment variable(Thomas)
Implement SET keyword = DEFAULT and SET TIME ZONE DEFAULT(Thomas) Implement SET keyword = DEFAULT and SET TIME ZONE DEFAULT(Thomas)
Enable SET TIME ZONE using TZ environment variable(Thomas) Enable SET TIME ZONE using TZ environment variable(Thomas)
Add PGDATESTYLE environment variable to frontend and backend initialization(Thomas) Add PGDATESTYLE environment variable to frontend and backend initialization(Tho
mas)
Add PGTZ, PGCOSTHEAP, PGCOSTINDEX, PGRPLANS, PGGEQO Add PGTZ, PGCOSTHEAP, PGCOSTINDEX, PGRPLANS, PGGEQO
frontend library initialization environment variables(Thomas) frontend library initialization environment variables(Thomas)
Regression tests time zone automatically set with "setenv PGTZ PST8PDT"(Thomas) Regression tests time zone automatically set with "setenv PGTZ PST8PDT"(Thomas)
...@@ -321,7 +315,6 @@ Add UNION, GROUP, DISTINCT to INSERT(Bruce) ...@@ -321,7 +315,6 @@ Add UNION, GROUP, DISTINCT to INSERT(Bruce)
varchar() stores only necessary bytes on disk(Bruce) varchar() stores only necessary bytes on disk(Bruce)
Fix for BLOBs(Peter) Fix for BLOBs(Peter)
Mega-Patch for JDBC...see README_6.3 for list of changes(Peter) Mega-Patch for JDBC...see README_6.3 for list of changes(Peter)
Allow installation data block size and max tuple size configuration(Darren)
Remove unused "option" from PQconnectdb() Remove unused "option" from PQconnectdb()
New LOCK command and lock manual page describing deadlocks(Bruce) New LOCK command and lock manual page describing deadlocks(Bruce)
Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce) Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce)
...@@ -336,8 +329,17 @@ Add Unix socket support to DBD::Pg(Goran) ...@@ -336,8 +329,17 @@ Add Unix socket support to DBD::Pg(Goran)
New python interface (PyGreSQL 2.0)(D'Arcy) New python interface (PyGreSQL 2.0)(D'Arcy)
New frontend/backend protocol has a version number, network byte order(Phil) New frontend/backend protocol has a version number, network byte order(Phil)
Security features in pg_hba.conf enhanced and documented, many cleanups(Phil) Security features in pg_hba.conf enhanced and documented, many cleanups(Phil)
New HTML and Postscript documentation(Thomas) CHAR() now faster access than VARCHAR() or TEXT
ecpg embedded SQL preprocessor
Add GROUP BY to INSERT INTO table SELECT * FROM table2
Reduce system column overhead(Vadmin)
Remove pg_time table(Vadim)
Add pg_type attribute to identify types that need length (bpchar, varchar)
Add report of offending line when COPY command fails
Allow VIEW permissions to be set separately from the underlying tables.
For security, use GRANT/REVOKE on views as appropriate(Jan)
Tables now have no default GRANT SELECT TO PUBLIC. You must
explicitly grant such permissions.
Source Tree Changes Source Tree Changes
------------------- -------------------
...@@ -374,3 +376,5 @@ Start an AUX port ...@@ -374,3 +376,5 @@ Start an AUX port
Start a Cygnus port Start a Cygnus port
Add string functions to regression suite(Thomas) Add string functions to regression suite(Thomas)
Expand a few function names formerly truncated to 16 characters(Thomas) Expand a few function names formerly truncated to 16 characters(Thomas)
Remove un-needed malloc() calls and replace with palloc()(Bruce)
migration/6.2.1_to_6.3
View file @ f0410b1e
This migration requires a complete dump of the 6.2 or 6.2.1 database and a This migration requires a complete dump of the 6.2 or 6.2.1 database and a
restore of the database in 6.3. restore of the database in 6.3.
In addition, 6.3 has separate permissions for views, rather than relying There are some general 6.3 issues that I want to mention. These are
on the permissions set on the underlying tables. For this reason, you will only the big items that can not be described in one sentence. A review
have to set permissions on your views if you want anything but the default of the HISTORY files is still needed.
permissions.
First, we now have subselects. Now that we have them, I would like to
6.3 has had its default permissions on a table set such that unless you mention that without subselects, SQL is a very limited language.
are the owner, when a table is created, other users of the system won't Subselects are a major feature, and you should review your code for
have access to them. You *must* do a 'GRANT' for each table you wish open places where subselects provide a better solution for your queries. I
to other ppl. think you will find that there are more uses for subselects than you may
think. Vadim has put us on the big SQL map with subselects, and fully
Those migrating from earlier 1.* releases should first upgrade to 1.09 functional ones too. The only thing you can't do with subselects is to
because the COPY output format was improved from the 1.02 release. use them in the target list.
Second, 6.3 uses unix domain sockets rather than TCP/IP by default. To
enable connections from other machines, you have to use the new
postmaster -i option, and of course edit pg_hba.conf. Also, for this
reason, the format of pg_hba.conf has changed.
Third, char() fields will now allow faster access than varchar() or
text. Specifically, the text and varchar() have a penalty for access to
any columns after the first column of this type. char() used to also
have this access penalty, but it no longer does. This may suggest that
you redesign some of your tables, especially if you have short character
columns that you have defined as varchar() or text. This and other
changes make 6.3 even faster than earlier releases.
We now have passwords definable independent of any Unix file. There are
new SQL USER commands. See the pg_hba.conf manual page for more
information. There is a new table, pg_shadow, which is used to store
user information and user passwords, and it by default only SELECT-able
by the postgres super-user. pg_user is now a view of pg_shadow, and is
SELECT-able by PUBLIC. You should keep using pg_user in your
application without changes.
User-created tables now no longer have SELECT permission to PUBLIC by
default. This was done because the ANSI standard requires it. You can
of course GRANT any permissions you want after the table is created.
System tables continue to be SELECT-able by PUBLIC.
We also have real deadlock detection code. No more sixty-second
timeouts. And the new locking code implements a FIFO better, so there
should be less resource starvation during heavy use. For performance
reasons, time travel is gone, but can be implemented using triggers (see
pgsql/contrib/spi/README). Please check out the new \d command for
types, operators, etc. Also, views have their own permissions now, not
based on the underlying tables, so permissions on them have to be set
separately. Check /pgsql/interfaces for some new ways to talk to
PostgreSQL.
This is the first release that really required an explaination for
existing users. In many ways, this was necessary because the new
release removes many limitations, and the work-arounds people were using
are no longer needed.
Long live PostgreSQL.
-- Bruce Momjian
register.txt
View file @ f0410b1e
(1998-02-01) (1998-03-01)
PostgreSQL has a Web site at http://www.postgresql.org/ which carries details PostgreSQL has a Web site at http://www.postgresql.org/ which carries details
on the latest release, upcoming features, and other information to make your on the latest release, upcoming features, and other information to make your
work or play with PostgreSQL more productive. work or play with PostgreSQL more productive.
......
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