projects / postgresql.git / commitdiff
| author | Bruce Momjian | |
| Mon, 22 Jan 2001 05:56:26 +0000 (05:56 +0000) | ||
| committer | Bruce Momjian | |
| Mon, 22 Jan 2001 05:56:26 +0000 (05:56 +0000) |
| doc/FAQ | patch | blob | blame | history | |
| doc/src/FAQ/FAQ.html | patch | blob | blame | history |
Last updated: Tue Oct 17 00:21:20 EDT 2000
Current maintainer: Bruce Momjian (
Current maintainer: Bruce Momjian ( The most recent version of this document can be viewed at The most recent version of this document can be viewed at Platform-specific questions are answered at Platform-specific questions are answered at 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 PostQuel query language with an extended subset of SQL. PostgreSQL is free and the complete source is available. PostgreSQL development is performed by a team of Internet developers who all subscribe to the PostgreSQL development mailing list. The current coordinator is Marc G. Fournier ( The authors of PostgreSQL 1.01 were Andrew Yu and Jolly Chen. Many others have contributed to the porting, testing, debugging, and enhancement of the code. The original Postgres code, from which PostgreSQL is derived, was the effort of many graduate students, undergraduate students, and staff programmers working under the direction of Professor Michael Stonebraker at the University of California, Berkeley. The original name of the software at Berkeley was Postgres. When SQL functionality was added in 1995, its name was changed to Postgres95. The name was changed at the end of 1996 to PostgreSQL. PostgreSQL is an enhancement of the POSTGRES database management PostgreSQL development is performed by a team of Internet The authors of PostgreSQL 1.01 were Andrew Yu and Jolly Chen. The original name of the software at Berkeley was Postgres. When It is pronounced Post-Gres-Q-L. PostgreSQL Data Base Management System Portions copyright (c) 1996-2000, PostgreSQL, Inc Portions Copyright (c) 1994-6 Regents of the University of California Portions copyright (c) 1996-2000, PostgreSQL, Inc Portions Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. Permission to use, copy, modify, and distribute this software IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY In general, a modern Unix-compatible platform should be able to run PostgreSQL. The platforms that had received explicit testing at the time of release are listed in the installation instructions. In general, a modern Unix-compatible platform should be able to It is possible to compile the libpq C library, psql, and other interfaces and binaries to run on MS Windows platforms. In this case, the client is running on MS Windows, and communicates via TCP/IP to a server running on one of our supported Unix platforms. A file win31.mak is included in the distribution for making a Win32 libpq library and psql. It is possible to compile the libpq C library, psql, and The database server can run on Windows NT and later using Cygwin, the Cygnus Unix/NT porting library. See pgsql/doc/FAQ_MSWIN in the distribution. The database server does not run on MS Windows 9X because Cygwin does not support the required features on those platforms. We have no plans to do a native port to any Microsoft platform. The database server can run on Windows NT and later using The primary anonymous ftp site for PostgreSQL is The primary anonymous ftp site for PostgreSQL is There is no support for PostgreSQL from the University of California, Berkeley. It is maintained through volunteer effort. There is no support for PostgreSQL from the University of The main mailing list is: The main mailing list is: to There is also a digest list available. To subscribe to this list, send email to: There is also a digest list available. To subscribe to this The bugs mailing list is available. To subscribe to this list, send email to The bugs mailing list is available. To subscribe to this list, Additional mailing lists and information about PostgreSQL can be found via the PostgreSQL WWW home page at: Additional mailing lists and information about PostgreSQL can be There is also an IRC channel on EFNet, channel #PostgreSQL. I use the unix command There is also an IRC channel on EFNet, channel A list of commercial PostgreSQL support is available at A list of commercial PostgreSQL support is available at Several manuals, manual pages, and some small test examples are included in the distribution. See the /doc directory. You can also browse the manual online at Several manuals, manual pages, and some small test examples are There is a PostgreSQL book available at There is a PostgreSQL book available at psql has some nice \d commands to show information about types, operators, functions, aggregates, etc. psql has some nice \d commands to show information about Our Web site contains even more documentation. PostgreSQL supports an extended subset of SQL-92. See our PostgreSQL supports an extended subset of SQL-92. The PostgreSQL book at The PostgreSQL book at Another one is "Teach Yourself SQL in 21 Days, Second Edition" at Another one is "Teach Yourself SQL in 21 Days, Second Edition" Many of our users like The Practical SQL Handbook, Bowman, Judith S., et al., Addison-Wesley. Others like The Complete Reference SQL, Groff et al., McGraw-Hill. Many of our users like The Practical SQL Handbook, Yes, we easily handle dates past the year 2000AD, and before 2000BC. Yes, we easily handle dates past the year 2000AD, and before First, download the latest source and read the PostgreSQL Developers documentation on our Web site, or in the distribution. Second, subscribe to the pgsql-hackers and pgsql-patches mailing lists. Third, submit high-quality patches to pgsql-patches. First, download the latest source and read the PostgreSQL There are about a dozen people who have commit privileges to the PostgreSQL CVS archive. They each have submitted so many high-quality patches that it was impossible for the existing committers to keep up, and we had confidence that patches they committed were of high quality. There are about a dozen people who have commit privileges to the Fill out the "bug-template" file and send it to: Fill out the "bug-template" file and send it to: Also check out our ftp site Also check out our ftp site There are several ways of measuring software: features, performance, reliability, support, and price. There are several ways of measuring software: features, There are two ODBC drivers available, PsqlODBC and OpenLink ODBC. There are two ODBC drivers available, PsqlODBC PsqlODBC is included in the distribution. More information about it can be gotten from PsqlODBC is included in the distribution. More information about OpenLink ODBC can be gotten from OpenLink ODBC can be gotten from They will probably be selling this product to people who need commercial-quality support, but a freeware version will always be available. Questions to They will probably be selling this product to people who need See also the See also the A nice introduction to Database-backed Web pages can be seen at: A nice introduction to Database-backed Web pages can be seen at: There is also one at There is also one at For Web integration, PHP is an excellent interface. It is at For Web integration, PHP is an excellent interface. It is at For complex cases, many use the Perl interface and CGI.pm. A WWW gateway based on WDB using Perl can be downloaded from A WWW gateway based on WDB using Perl can be downloaded from We have a nice graphical user interface called pgaccess, which is shipped as part of the distribution. Pgaccess also has a report generator. The Web page is We have a nice graphical user interface called pgaccess, We also include ecpg, which is an embedded SQL query language interface for C. We also include ecpg, which is an embedded SQL query We have: Specify the --prefix option when running configure. It could be a variety of problems, but first check to see that you have System V extensions installed in your kernel. PostgreSQL requires kernel support for shared memory and semaphores. You either do not have shared memory configured properly in your kernel or you need to enlarge the shared memory available in the kernel. The exact amount you need depends on your architecture and how many buffers and backend processes you configure for the postmaster. For most systems, with default numbers of buffers and processes, you need a minimum of ~1MB. If the error message is IpcSemaphoreCreate: semget failed (No space left on device) then your kernel is not configured with enough semaphores. Postgres needs one semaphore per potential backend process. A temporary solution is to start the postmaster with a smaller limit on the number of backend processes. Use -N with a parameter less than the default of 32. A more permanent solution is to increase your kernel's SEMMNS and SEMMNI parameters. If the error message is something else, you might not have semaphore support configured in your kernel at all. By default, PostgreSQL only allows connections from the local machine using Unix domain sockets. Other machines will not be able to connect unless you add the -i flag to the postmaster, and enable host-based authentication by modifying the file $PGDATA/pg_hba.conf accordingly. This will allow TCP/IP connections. The default configuration allows only unix domain socket connections from the local machine. To enable TCP/IP connections, make sure the postmaster has been started with the -i option, and add an appropriate host entry to the file pgsql/data/pg_hba.conf. This problem can be caused by a kernel that is not configured to support semaphores. Certainly, indices can speed up queries. The EXPLAIN command allows you to see how PostgreSQL is interpreting your query, and which indices are being used. If you are doing a lot of INSERTs, consider doing them in a large batch using the COPY command. This is much faster than individual INSERTS. Second, statements not in a BEGIN WORK/COMMIT transaction block are considered to be in their own transaction. Consider performing several statements in a single transaction block. This reduces the transaction overhead. Also consider dropping and recreating indices when making large data changes. There are several tuning options. You can disable fsync() by 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 memory buffers used by the backend processes. If you make this parameter too high, the postmaster may not start because you've exceeded your kernel's limit on shared memory space. Each buffer is 8K and the default is 64 buffers. You can also use the backend -S option to increase the maximum amount of memory used by the backend process for temporary sorts. The -S value is measured in kilobytes, and the default is 512 (ie, 512K). You can also use the CLUSTER command to group data in tables to match an index. See the CLUSTER manual page for more details. PostgreSQL has several features that report status information that can be valuable for debugging purposes. First, by running configure with the --enable-cassert option, many assert()'s monitor the progress of the backend and halt the program when something unexpected occurs. 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: Specify the --prefix option when running It could be a variety of problems, but first check to see that You either do not have shared memory configured properly in your If the error message is IpcSemaphoreCreate: semget failed (No If the error message is something else, you might not have By default, PostgreSQL only allows connections from the local The default configuration allows only unix domain socket This problem can be caused by a kernel that is not configured to Certainly, indices can speed up queries. The If you are doing a lot of INSERTs, consider doing There are several tuning options. You can disable fsync() You can also use the postmaster -B option to You can also use the backend -S option to increase the You can also use the CLUSTER command to group PostgreSQL has several features that report status information First, by running configure with the --enable-cassert Both postmaster and postgres have several debug This will put a server.log file in the top-level PostgreSQL directory. This file contains useful information about problems or errors encountered by the server. Postmaster has a -d option that allows even more detailed information to be reported. The -d option takes a number that specifies the debug level. Be warned that high debug level values generate large log files. If the postmaster is not running, you can actually run the postgres backend from the command line, and type your SQL statement directly. This is recommended only for debugging purposes. Note that a newline terminates the query, not a semicolon. If you have compiled with debugging symbols, you can use a debugger to see what is happening. Because the backend was not started from the postmaster, it is not running in an identical environment and locking/backend interaction problems may not be duplicated. If the postmaster is running, start psql in one window, then find the PID of the postgres process used by psql. Use a debugger to attach to the postgres PID. You can set breakpoints in the debugger and issue queries from psql. If you are debugging postgres startup, you can set PGOPTIONS="-W n", then start psql. This will cause startup to delay for n seconds so you can attach with the debugger and trace through the startup sequence. The postgres program has -s, -A, and -t options that can be very useful for debugging and performance measurements. You can also compile with profiling to see what functions are taking 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 client's current directory. You need to increase the postmaster's limit on how many concurrent backend processes it can start. In PostgreSQL 6.5 and up, the default limit is 32 processes. You can increase it by restarting the postmaster with a suitable -N value. With the default configuration you can set -N as large as 1024. If you need more, increase MAXBACKENDS in include/config.h and rebuild. You can set the default value of -N at configuration time, if you like, using configure's --with-maxbackends switch. Note that if you make -N larger than 32, you must also increase -B beyond its default of 64; -B must be at least twice -N, and probably should be more than that for best performance. For large numbers of backend processes, you are also likely to find that you need to increase various Unix kernel configuration parameters. Things to check include the maximum size of shared memory blocks, SHMMAX; the maximum number of semaphores, SEMMNS and SEMMNI; the maximum number of processes, NPROC; the maximum number of processes per user, MAXUPRC; and the maximum number of open files, NFILE and NINODE. The reason that PostgreSQL has a limit on the number of allowed backend processes is so your system won't run out of resources. In PostgreSQL versions prior to 6.5, the maximum number of backends was 64, and changing it required a rebuild after altering the MaxBackendId constant in include/storage/sinvaladt.h. They are temporary files generated by the query executor. For example, if a sort needs to be done to satisfy an ORDER BY, and the sort requires more space than the backend's -S parameter allows, then temporary files are created to hold the extra data. The temporary files should be deleted automatically, but might not if a backend crashes during a sort. If you have no backends running at the time, it is safe to delete the pg_tempNNN.NN files. This will put a server.log file in the top-level PostgreSQL If the postmaster is not running, you can actually run If the postmaster is running, start psql in one The postgres program has -s, -A, and -t You can also compile with profiling to see what functions are You need to increase the postmaster's limit on how many In PostgreSQL 6.5 and up, the default limit is 32 processes. You Note that if you make -N larger than 32, you must also In PostgreSQL versions prior to 6.5, the maximum number of They are temporary files generated by the query executor. For The temporary files should be deleted automatically, but might Check your locale configuration. PostgreSQL uses the locale setting of the user that ran the postmaster process. There are postgres and psql SET commands to control the date format. Set those accordingly for your operating environment. Check your locale configuration. PostgreSQL uses the locale See the DECLARE manual page for a description. See the DECLARE manual page for a See the FETCH manual page, or use SELECT ... LIMIT.... See the FETCH manual page, or use The entire query may have to be evaluated, even if you only want the first few rows. Consider a query that has an ORDER BY. If there is an index that matches the ORDER BY, PostgreSQL may be able to evaluate only the first few records requested, or the entire query may have to be evaluated until the desired rows have been generated. The entire query may have to be evaluated, even if you only want You can read the source code for psql in file pgsql/src/bin/psql/describe.c. It contains SQL commands that generate the output for psql's backslash commands. You can also start psql with the -E option so it will print out the queries it uses to execute the commands you give. You can read the source code for psql in file We do not support ALTER TABLE DROP COLUMN, but do this: We do not support ALTER TABLE DROP COLUMN, but do These are the limits: A PostgreSQL database may need six-and-a-half times the disk space required to store the data in a flat file. A PostgreSQL database may need six-and-a-half times the disk Consider a file of 300,000 lines with two integers on each line. The flat file is 2.4MB. The size of the PostgreSQL database file containing this data can be estimated at 14MB: Consider a file of 300,000 lines with two integers on each line. Indexes do not require as much overhead, but do contain the data that is being indexed, so they can be large also. Indexes do not require as much overhead, but do contain the data psql has a variety of backslash commands to show such information. Use \? to see them. psql has a variety of backslash commands to show such Also try the file pgsql/src/tutorial/syscat.source. It illustrates many of the SELECTs needed to get information from the database system tables. Also try the file pgsql/src/tutorial/syscat.source. It PostgreSQL does not automatically maintain statistics. VACUUM must be run to update the statistics. After statistics are updated, the optimizer knows how many rows in the table, and can better decide if it should use indices. Note that the optimizer does not use indices in cases when the table is small because a sequential scan would be faster. PostgreSQL does not automatically maintain statistics. For column-specific optimization statistics, use VACUUM ANALYZE. VACUUM ANALYZE is important for complex multijoin queries, so the optimizer can estimate the number of rows returned from each table, and choose the proper join order. The backend does not keep track of column statistics on its own, so VACUUM ANALYZE must be run to collect them periodically. For column-specific optimization statistics, use VACUUM Indexes are usually not used for ORDER BY operations: a sequential scan followed by an explicit sort is faster than an indexscan of all tuples of a large table, because it takes fewer disk accesses. Indexes are usually not used for ORDER BY When using wild-card operators such as LIKE or ~, indices can only be used if the beginning of the search is anchored to the start of the string. So, to use indices, LIKE searches should not begin with %, and ~(regular expression searches) should start with ^. When using wild-card operators such as LIKE or See the EXPLAIN manual page. 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 an R-tree index can be built on an attribute of type point, the system can more efficiently answer queries such as "select all points within a bounding rectangle." The canonical paper that describes the original R-tree design is: Guttman, A. "R-trees: A Dynamic Index Structure for Spatial Searching." Proc of the 1984 ACM SIGMOD Int'l Conf on Mgmt of Data, 45-57. You can also find this paper in Stonebraker's "Readings in Database Systems". Built-in R-trees can handle polygons and boxes. In theory, R-trees can be extended to handle higher number of dimensions. In practice, extending R-trees requires a bit of work and we don't currently have any documentation on how to do it. The GEQO module speeds query optimization when joining many tables by means of a Genetic Algorithm (GA). It allows the handling of large join queries through nonexhaustive search. The ~ operator does regular expression matching, and ~* does case-insensitive regular expression matching. There is no case-insensitive variant of the LIKE operator, but you can get the effect of case-insensitive LIKE with this: An R-tree index is used for indexing spatial data. A hash index The canonical paper that describes the original R-tree design Guttman, A. "R-trees: A Dynamic Index Structure for Spatial You can also find this paper in Stonebraker's "Readings in Built-in R-trees can handle polygons and boxes. In theory, The GEQO module speeds query optimization when The ~ operator does regular expression matching, and You test the column with IS NULL and IS NOT NULL. You test the column with IS NULLIS NOT NULL. You will see the internal name when examining system catalogs and in some error messages. You will see the internal name when examining system catalogs The last four types above are "varlena" types (i.e., the first four bytes on disk are the length, followed by the data). Thus the actual space used is slightly greater than the declared size. However, these data types are also subject to compression or being stored out-of-line by TOAST, so the space on disk might also be less than expected. The last four types above are "varlena" types (i.e., the first PostgreSQL supports a SERIAL data type. It auto-creates a sequence and index on the column. For example, this: PostgreSQL supports a SERIAL data type. It One approach is to to retrieve the next SERIAL value from the sequence object with the nextval() function before inserting and then insert it explicitly. Using the example table in One approach is to to retrieve the next SERIAL Alternatively, you could retrieve the assigned SERIAL value with the currval() function after it was inserted by default, e.g., Alternatively, you could retrieve the assigned No. This is handled by the backends. OIDs are PostgreSQL's answer to unique row ids. Every row that is created in PostgreSQL gets a unique OID. All OIDs generated during initdb are less than 16384 (from backend/access/transam.h). All user-created OIDs are equal to or greater than this. By default, all these OIDs are unique not only within a table or database, but unique within the entire PostgreSQL installation. PostgreSQL uses OIDs in its internal system tables to link rows between 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. You can create an index on the OID field for faster access. Oids are assigned to all new rows from a central area that is used by all databases. If you want to change the OID to something else, or if you want to make a copy of the table, with the original OID's, there is no reason you can't do it: OIDs are PostgreSQL's answer to unique row ids. PostgreSQL uses OIDs in its internal system Oids are assigned to all new rows from a central OIDs are stored as 4-byte integers, and will overflow at 4 billion. No one has reported this ever happening, and we plan to have the limit removed before anyone does. OIDs are stored as 4-byte integers, and will TIDs are used to identify specific physical rows with block and offset values. Tids change after rows are modified or reloaded. They are used by index entries to point to physical rows. TIDs are used to identify specific physical rows Some of the source code and older documentation use terms that have more common usage. Here are some: Some of the source code and older documentation use terms that A list of general database terms can be found at: A list of general database terms can be found at: It is possible you have run out of virtual memory on your system, or your kernel has a low limit for certain resources. Try this before starting the postmaster: It is possible you have run out of virtual memory on your From psql, type You need to put You need to put Currently PostgreSQL enforces the rule by closing large object handles at transaction commit. So the first attempt to do anything with the handle will draw invalid large obj descriptor. So code that used to work (at least most of the time) will now generate that error message if you fail to use a transaction. Currently PostgreSQL enforces the rule by closing large object If you are using a client interface like ODBC you may need to set If you are using a client interface like ODBC you Use now(): Currently, we join subqueries to outer queries by sequentially scanning the result of the subquery for each row of the outer query. A workaround is to replace Currently, we join subqueries to outer queries by sequentially PostgreSQL 7.1 and later supports outer joins. In previous releases, outer joins can be simulated using UNION and NOT IN. For example, when joining tab1 and tab2, the following query does an outer join of the two tables: PostgreSQL 7.1 and later supports outer joins. Here is an The problem could be a number of things. Try testing your user-defined function in a stand-alone test program first. The problem could be a number of things. Try testing your You are pfree'ing something that was not palloc'ed. Beware of mixing malloc/free and palloc/pfree. You are pfree'ing something that was not Send your extensions to the pgsql-hackers mailing list, and they will eventually end up in the contrib/ subdirectory. Send your extensions to the pgsql-hackers mailing list, This requires wizardry so extreme that the authors have never tried it, though in principle it can be done. This requires wizardry so extreme that the authors have never The Makefiles do not have the proper dependencies for include files. You have to do a make clean and then another make. If you are using GCC you can use the --enable-depend option of configure to have the compiler compute the dependencies automatically. The Makefiles do not have the proper dependencies for
-
+ + href=
+ "http://www.Postgresql.org/docs/faq-english.html">http://www.PostgreSQL.org/docs/faq-english.html.
-
+ + "http://www.PostgreSQL.org/docs/">http://www.PostgreSQL.org/docs/.
-
+
+ on?
-
-
+
+ missing features?
+
-
+
+ DBMS's?
User Client Questions
-
-
-
-
+
+ PostgreSQL?
+
+ PostgreSQL to Web pages?
+
+ interface? A report generator? An embedded query language
+ interface?
+
+ communicate with PostgreSQL?
Administrative Questions
-
-
-
-
-
-
-
-
+
+ than /usr/local/pgsql?
+
+ a Bad System Call or core dumped message. Why?
+
+ I get IpcMemoryCreate errors. Why?
+
+ I get IpcSemaphoreCreate errors. Why?
+
+ accessing my PostgreSQL database?
+
+ another machine?
+
+ table access. Why?
+
+ better performance?
-
-
+
+ when trying to connect. Why?
+
+ files in my database directory?
Operational Questions
-
-
-
-
-
-
-
-
-
-
+
+ decimal points, and date formats.
+
+ binary cursors and normal cursors?
+
+ first few rows of a query?
+
+ things I can see in psql?
+
+ table?
+
+ database?
+
+ to store data from a typical text file?
+
+ operations are defined in the database?
+
+ the indexes. Why?
+
+ evaluating my query?
-
-
-
-
-
-
-
-
-
-
-
-
-
IN so slow?+
+ and case-insensitive regular expression searches?
+
+ is NULL?
+
+ various character types?
+
+ serial/auto-incrementing field?
+
+ SERIAL insert?
+
+ nextval() lead to a race condition with other users?
+
+ TID?
+
+ used in PostgreSQL?
+
+ failure: memory exhausted?"
+
+ am running?
+
+ invalid large obj descriptor. Why?
+
+ default to the current time?
+
+
IN so slow?
Extending PostgreSQL
-
-
-
-
-
+
+ it in psql, why does it dump core?
+
+ "NOTICE:PortalHeapMemoryFree: 0x402251d0 not in alloc set!"
+ mean?
+
+ and functions to PostgreSQL?
+
+ tuple?
+
+ recompile not see the change?
-
-
-
-
-
-
-
+
+ system, a next-generation DBMS research prototype.
+ While PostgreSQL retains 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 and the
+ complete source is available.
+
+
+ developers who all subscribe to the PostgreSQL development mailing
+ list. The current coordinator is Marc G. Fournier (+ "mailto:[email protected]">[email protected]). (See
+ below on how to join). This team is now responsible for all
+ development of PostgreSQL.
+
+
+ Many others have contributed to the porting, testing, debugging,
+ and enhancement of the code. The original Postgres code, from which
+ PostgreSQL is derived, was the effort of many graduate students,
+ undergraduate students, and staff programmers working under the
+ direction of Professor Michael Stonebraker at the University of
+ California, Berkeley.
+
+
+ SQL functionality was added in 1995, its name was
+ changed to Postgres95. The name was changed at the end of 1996 to
+ PostgreSQL.
-
+
+ Copyright (c) 1994-6 Regents of the University of California
-
+
+ and its documentation for any purpose, without fee, and without a
+ written agreement is hereby granted, provided that the above
+ copyright notice and this paragraph and the following two
+ paragraphs appear in all copies.
-
+
+ PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
+ DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS
+ SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF
+ CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
+
+ WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
+ SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE
+ UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE,
+ SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
-
+
+ on?
-
+
+ run PostgreSQL. The platforms that had received explicit testing at
+ the time of release are listed in the installation
+ instructions.
-
+
Client
+
+
+ other interfaces and binaries to run on MS Windows platforms. In
+ this case, the client is running on MS Windows, and communicates
+ via TCP/IP to a server running on one of our supported Unix
+ platforms. A file win31.mak is included in the distribution
+ for making a Win32 libpq library and psql. PostgreSQL also
+ communicates with ODBC clients.
-
+
Server
+
+
+ Cygwin, the Cygnus Unix/NT porting library. See
+ pgsql/doc/FAQ_MSWIN in the distribution or the MS Windows
+ FAQ on our web site. The database server does not run on MS Windows
+ 9X because Cygwin does not support the required features on those
+ platforms. We have no plan to do a native port to any Microsoft
+ platform.
-
+ + "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub.
+ For mirror sites, see our main Web site.
-
+
+ California, Berkeley. It is maintained through volunteer
+ effort.
-
+ + "mailto:[email protected]">[email protected].
+ It is available for discussion of matters pertaining to PostgreSQL.
+ To subscribe, send mail with the following lines in the body (not
+ the subject line)
subscribe
end
-
+ + "mailto:[email protected]">[email protected].
-
+
+ list, send email to: + "mailto:[email protected]">[email protected]
+ with a body of:
subscribe
end
- Digests are sent out to members of this list whenever the main list has received around 30k of messages.
+ Digests are sent out to members of this list whenever the main list
+ has received around 30k of messages.
-
+
+ send email to + "mailto:[email protected]">[email protected]
+ with a body of:
subscribe
end
- There is also a developers discussion mailing list available. To subscribe to this list, send email to
+ There is also a developers discussion mailing list available. To
+ subscribe to this list, send email to + "mailto:[email protected]">[email protected]
+ with a body of:
subscribe
end
-
+
+ found via the PostgreSQL WWW home page at:
-
irc -c '#PostgreSQL' "$USER" irc.phoenix.net.+
+ #PostgreSQL. I use the unix command
irc -c+ '#PostgreSQL' "$USER" irc.phoenix.net.
-
+ + "http://www.postgresql.org/users-lounge/commercial-support.html">http://www.postgresql.org/users-lounge/commercial-support.html.
-
+
+ included in the distribution. See the /doc directory. You
+ can also browse the manual online at + "http://www.PostgreSQL.org/docs/postgres">http://www.PostgreSQL.org/docs/postgres.
-
+ + "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html.
-
+
+ types, operators, functions, aggregates, etc.
-
+
+ missing features?
-
+
+ See our
+ list for known bugs, missing features, and future plans.
-
+
+ SQL?
-
+ + "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html
+ teaches SQL. There is a nice tutorial at + "http://w3.one.net/~jhoffman/sqltut.htm">http://w3.one.net/~jhoffman/sqltut.htm
+ and at + "http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
+ http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM.
-
+
+ at + "http://members.tripod.com/er4ebus/sql/index.htm">http://members.tripod.com/er4ebus/sql/index.htm
-
+
+ Bowman, Judith S., et al., Addison-Wesley. Others like The
+ Complete Reference SQL, Groff et al., McGraw-Hill.
-
+
+ 2000BC.
-
+
+ team?
-
+
+ Developers documentation on our Web site, or in the distribution.
+ Second, subscribe to the pgsql-hackers and
+ pgsql-patches mailing lists. Third, submit high-quality
+ patches to pgsql-patches.
-
+
+ PostgreSQL CVS archive. They each have submitted so
+ many high-quality patches that it was impossible for the existing
+ committers to keep up, and we had confidence that patches they
+ committed were of high quality.
-
+ + "mailto:[email protected]">[email protected]
-
+ + "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub to
+ see if there is a more recent PostgreSQL version or patches.
-
+
+ DBMS's?
-
+
+ performance, reliability, support, and price.
-
+
+ DBMS's, like transactions, subselects, triggers,
+ views, foreign key referential integrity, and sophisticated
+ locking. We have some features they don't have, like user-defined
+ types, inheritance, rules, and multi-version concurrency control
+ to reduce lock contention.
-
+
+ flushes every completed transaction to disk, guaranteeing that if
+ the OS crashes or loses power in the next few seconds, all your
+ data is safely stored on disk. In this mode, we are slower than
+ most commercial databases, partly because few of them do such
+ conservative flushing to disk in their default modes. In
+ no-fsync mode, we are usually faster than commercial
+ databases, though in this mode, an OS crash could cause data
+ corruption. We are working to provide an intermediate mode that
+ suffers less performance overhead than full fsync mode, and will
+ allow data integrity within 30 seconds of an OS crash.
- In comparison to MySQL or leaner database systems, we are slower on inserts/updates because we have transaction overhead. Of course, MySQL doesn't have any of the features mentioned in the Features section above. We are built for flexibility and features, though we continue to improve performance through profiling and source code analysis. There is an interesting Web page comparing PostgreSQL to MySQL at
+ In comparison to MySQL or leaner database systems, we are slower
+ on inserts/updates because we have transaction overhead. Of
+ course, MySQL doesn't have any of the features mentioned in the
+ Features section above. We are built for flexibility and
+ features, though we continue to improve performance through
+ profiling and source code analysis. There is an interesting Web
+ page comparing PostgreSQL to MySQL at + "http://openacs.org/why-not-mysql.html">http://openacs.org/why-not-mysql.html
+
- We handle each user connection by creating a Unix process. Backend processes share data buffers and locking information. With multiple CPU's, multiple backends can easily run on different CPU's.
+ We handle each user connection by creating a Unix process.
+ Backend processes share data buffers and locking information.
+ With multiple CPU's, multiple backends can easily run on
+ different CPU's.
-
+
+ is worthless. We strive to release well-tested, stable code that
+ has a minimum of bugs. Each release has at least one month of
+ beta testing, and our release history shows that we can provide
+ stable, solid releases that are ready for production use. We
+ believe we compare favorably to other database software in this
+ area.
-
+
+ users to help resolve any problems encountered. While we can not
+ guarantee a fix, commercial DBMS's don't always
+ supply a fix either. Direct access to developers, the user
+ community, manuals, and the source code often make PostgreSQL
+ support superior to other DBMS's. There is
+ commercial per-incident support available for those who need it.
+ (See support FAQ item.)
-
+
+ You can add our code to your product with no limitations, except
+ those outlined in our BSD-style license stated above.
User Client Questions
-
+
+ for PostgreSQL?
-
+
+ and OpenLink ODBC.
-
+
+ it can be gotten from + "ftp://ftp.PostgreSQL.org/pub/odbc/">ftp://ftp.PostgreSQL.org/pub/odbc/.
-
+ + "http://www.openlinksw.com/">http://www.openlinksw.com. It
+ works with their standard ODBC client software so
+ you'll have PostgreSQL ODBC available on every
+ client platform they support (Win, Mac, Unix, VMS).
-
+
+ commercial-quality support, but a freeware version will always be
+ available. Questions to + "mailto:[email protected]">[email protected].
-
+ + "http://www.PostgreSQL.org/docs/programmer/odbc.htm">ODBC chapter
+ of the Programmer's Guide.
-
+
+ PostgreSQL to Web pages?
-
+
+
-
+ + "http://www.phone.net/home/mwm/hotlist/">http://www.phone.net/home/mwm/hotlist/.
-
+ + href="http://www.php.net">http://www.php.net
-
+ + href=
+ "http://www.eol.ists.ca/~dunlop/wdb-p95">http://www.eol.ists.ca/~dunlop/wdb-p95
-
+
+ interface? A report generator? An embedded query language
+ interface?
-
+
+ which is shipped as part of the distribution. Pgaccess also
+ has a report generator. The Web page is + "http://www.flex.ro/pgaccess">http://www.flex.ro/pgaccess
-
+
+ language interface for C.
-
+
+ communicate with PostgreSQL?
-
+ + "http://www.php.net">PHP from http://www.php.net)
Administrative Questions
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+ other than /usr/local/pgsql?
+
+
+ configure.
+
+
+ get a Bad System Call or core dumped message. Why?
+
+
+ you have System V extensions installed in your kernel. PostgreSQL
+ requires kernel support for shared memory and semaphores.
+
+
+ postmaster, I get IpcMemoryCreate errors. Why?
+
+
+ kernel or you need to enlarge the shared memory available in the
+ kernel. The exact amount you need depends on your architecture and
+ how many buffers and backend processes you configure for the
+ postmaster. For most systems, with default numbers of
+ buffers and processes, you need a minimum of ~1MB.
+
+
+ postmaster, I get IpcSemaphoreCreate errors.
+ Why?
+
+
+ space left on device) then your kernel is not configured with
+ enough semaphores. Postgres needs one semaphore per potential
+ backend process. A temporary solution is to start the
+ postmaster with a smaller limit on the number of backend
+ processes. Use -N with a parameter less than the default of
+ 32. A more permanent solution is to increase your kernel's
+ SEMMNS and SEMMNI parameters.
+
+
+ semaphore support configured in your kernel at all.
+
+
+ accessing my PostgreSQL database?
+
+
+ machine using Unix domain sockets. Other machines will not be able
+ to connect unless you add the -i flag to the
+ postmaster, and enable host-based authentication by
+ modifying the file $PGDATA/pg_hba.conf accordingly. This
+ will allow TCP/IP connections.
+
+
+ another machine?
+
+
+ connections from the local machine. To enable TCP/IP connections,
+ make sure the postmaster has been started with the -i
+ option, and add an appropriate host entry to the file
+ pgsql/data/pg_hba.conf.
+
+
+ table access. Why?
+
+
+ support semaphores.
+
+
+ better performance?
+
+
+ EXPLAIN command allows you to see how PostgreSQL is
+ interpreting your query, and which indices are being used.
+
+
+ them in a large batch using the COPY command. This
+ is much faster than individual INSERTS. Second,
+ statements not in a BEGIN WORK/COMMIT transaction
+ block are considered to be in their own transaction. Consider
+ performing several statements in a single transaction block. This
+ reduces the transaction overhead. Also consider dropping and
+ recreating indices when making large data changes.
+
+
+ by starting the postmaster with a -o -F option. This
+ will prevent fsync()'s from flushing to disk after every
+ transaction.
+
+
+ increase the number of shared memory buffers used by the backend
+ processes. If you make this parameter too high, the
+ postmaster may not start because you've exceeded your
+ kernel's limit on shared memory space. Each buffer is 8K and the
+ default is 64 buffers.
+
+
+ maximum amount of memory used by the backend process for temporary
+ sorts. The -S value is measured in kilobytes, and the
+ default is 512 (ie, 512K).
+
+
+ data in tables to match an index. See the CLUSTER
+ manual page for more details.
+
+
+ available?
+
+
+ that can be valuable for debugging purposes.
+
+
+ option, many assert()'s monitor the progress of the backend
+ and halt the program when something unexpected occurs.
+
+
+ options available. First, whenever you start the postmaster,
+ make sure you send the standard output and error to a log file,
+ like:
cd /usr/local/pgsql
./bin/postmaster >server.log 2>&1 &
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+ directory. This file contains useful information about problems or
+ errors encountered by the server. Postmaster has a -d
+ option that allows even more detailed information to be reported.
+ The -d option takes a number that specifies the debug level.
+ Be warned that high debug level values generate large log
+ files.
+
+
+ the postgres backend from the command line, and type your
+ SQL statement directly. This is recommended
+ only for debugging purposes. Note that a newline terminates
+ the query, not a semicolon. If you have compiled with debugging
+ symbols, you can use a debugger to see what is happening. Because
+ the backend was not started from the postmaster, it is not
+ running in an identical environment and locking/backend interaction
+ problems may not be duplicated.
+
+
+ window, then find the PID of the postgres
+ process used by psql. Use a debugger to attach to the
+ postgres PID. You can set breakpoints in the
+ debugger and issue queries from psql. If you are debugging
+ postgres startup, you can set PGOPTIONS="-W n", then start
+ psql. This will cause startup to delay for n seconds
+ so you can attach with the debugger and trace through the startup
+ sequence.
+
+
+ options that can be very useful for debugging and performance
+ measurements.
+
+
+ taking 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 client's current directory.
+
+
+ trying to connect. Why?
+
+
+ concurrent backend processes it can start.
+
+
+ can increase it by restarting the postmaster with a suitable
+ -N value. With the default configuration you can set
+ -N as large as 1024. If you need more, increase
+ MAXBACKENDS in include/config.h and rebuild.
+ You can set the default value of -N at configuration time,
+ if you like, using configure's --with-maxbackends
+ switch.
+
+
+ increase -B beyond its default of 64; -B must be at
+ least twice -N, and probably should be more than that for
+ best performance. For large numbers of backend processes, you are
+ also likely to find that you need to increase various Unix kernel
+ configuration parameters. Things to check include the maximum size
+ of shared memory blocks, SHMMAX; the maximum number
+ of semaphores, SEMMNS and SEMMNI; the
+ maximum number of processes, NPROC; the maximum
+ number of processes per user, MAXUPRC; and the
+ maximum number of open files, NFILE and
+ NINODE. The reason that PostgreSQL has a limit on
+ the number of allowed backend processes is so your system won't run
+ out of resources.
+
+
+ backends was 64, and changing it required a rebuild after altering
+ the MaxBackendId constant in
+ include/storage/sinvaladt.h.
+
+
+ files in my database directory?
+
+
+ example, if a sort needs to be done to satisfy an ORDER
+ BY, and the sort requires more space than the backend's
+ -S parameter allows, then temporary files are created to
+ hold the extra data.
+
+
+ not if a backend crashes during a sort. If you have no backends
+ running at the time, it is safe to delete the pg_tempNNN.NN
+ files.
Operational Questions
-
+
+ decimal points, and date formats.
-
+
+ setting of the user that ran the postmaster process. There
+ are postgres and psql SET commands to control the
+ date format. Set those accordingly for your operating
+ environment.
-
+
+ binary cursors and normal cursors?
-
+
+ description.
-
+
+ first few rows of a query?
-
+
+ SELECT ... LIMIT....
-
+
+ the first few rows. Consider a query that has an ORDER
+ BY. If there is an index that matches the ORDER
+ BY, PostgreSQL may be able to evaluate only the first few
+ records requested, or the entire query may have to be evaluated
+ until the desired rows have been generated.
-
+
+ things I can see in psql?
-
+
+ pgsql/src/bin/psql/describe.c. It contains
+ SQL commands that generate the output for psql's
+ backslash commands. You can also start psql with the
+ -E option so it will print out the queries it uses to
+ execute the commands you give.
-
+
+ table?
-
+
+ this:
SELECT ... -- select all columns but the one you want to remove
INTO TABLE new_table
ALTER TABLE new_table RENAME TO old_table;
-
+
+ table, database?
Maximum number of columns in a table? unlimited
Maximum number of indexes on a table? unlimited
- Of course, these are not actually unlimited, but limited to available disk space.
+ Of course, these are not actually unlimited, but limited to
+ available disk space.
-
+
+ to store data from a typical text file?
-
+
+ space required to store the data in a flat file.
-
+
+ The flat file is 2.4MB. The size of the PostgreSQL database file
+ containing this data can be estimated at 14MB:
36 bytes: each row header (approximate)
+ 8 bytes: two int fields @ 4 bytes each
1755 database pages * 8192 bytes per page = 14,376,960 bytes (14MB)
-
+
+ that is being indexed, so they can be large also.
-
+
+ operations are defined in the database?
-
+
+ information. Use \? to see them.
-
+
+ illustrates many of the SELECTs needed to get
+ information from the database system tables.
-
+
+ the indexes. Why?
-
+
+ VACUUM must be run to update the statistics. After
+ statistics are updated, the optimizer knows how many rows in the
+ table, and can better decide if it should use indices. Note that
+ the optimizer does not use indices in cases when the table is small
+ because a sequential scan would be faster.
-
+
+ ANALYZE. VACUUM ANALYZE is important for
+ complex multijoin queries, so the optimizer can estimate the number
+ of rows returned from each table, and choose the proper join order.
+ The backend does not keep track of column statistics on its own, so
+ VACUUM ANALYZE must be run to collect them
+ periodically.
-
+
+ operations: a sequential scan followed by an explicit sort is
+ faster than an indexscan of all tuples of a large table, because it
+ takes fewer disk accesses.
-
+
+ ~, indices can only be used if the beginning of the search
+ is anchored to the start of the string. So, to use indices,
+ LIKE searches should not begin with %, and
+ ~(regular expression searches) should start with
+ ^.
-
+
+ is evaluating my query?
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+ 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 an R-tree index can be
+ built on an attribute of type point, the system can more
+ efficiently answer queries such as "select all points within a
+ bounding rectangle."
+
+
+ is:
+
+
+ Searching." Proc of the 1984 ACM SIGMOD Int'l Conf on Mgmt of Data,
+ 45-57.
+
+
+ Database Systems".
+
+
+ R-trees can be extended to handle higher number of dimensions. In
+ practice, extending R-trees requires a bit of work and we don't
+ currently have any documentation on how to do it.
+
+
+ Optimization?
+
+
+ joining many tables by means of a Genetic Algorithm (GA). It allows
+ the handling of large join queries through nonexhaustive
+ search.
+
+
+ searches and case-insensitive regular expression searches?
+
+
+ ~* does case-insensitive regular expression matching. There
+ is no case-insensitive variant of the LIKE operator,
+ but you can get the effect of case-insensitive LIKE
+ with this:
WHERE lower(textfield) LIKE lower(pattern)
-
+
+ is NULL?
-
+
-
+
+ various character types?
Type Internal Name Notes
--------------------------------------------------
BYTEA bytea variable-length byte array (null-safe)
-
+
+ and in some error messages.
-
+
+ four bytes on disk are the length, followed by the data). Thus the
+ actual space used is slightly greater than the declared size.
+ However, these data types are also subject to compression or being
+ stored out-of-line by TOAST, so the space on disk
+ might also be less than expected.
-
+
+ serial/auto-incrementing field?
-
+
+ auto-creates a sequence and index on the column. For example,
+ this:
CREATE TABLE person (
id SERIAL,
);
CREATE UNIQUE INDEX person_id_key ON person ( id );
- See the create_sequence manual page for more information about sequences. You can also use each row's OID field as a unique value. However, if you need to dump and reload the database, you need to use pg_dump's -o option or COPY WITH OIDS option to preserve the OIDs.
-
-
-
-
-
-
+ See the create_sequence manual page for more information
+ about sequences. You can also use each row's OID field as a
+ unique value. However, if you need to dump and reload the database,
+ you need to use pg_dump's -o option or COPY WITH
+ OIDS option to preserve the OIDs.
+
+
+ Rows.
+
+
+ SERIAL insert?
+
+
+ value from the sequence object with the nextval() function
+ before inserting and then insert it explicitly. Using the
+ example table in
+ this:
$newSerialID = nextval('person_id_seq');
INSERT INTO person (id, name) VALUES ($newSerialID, 'Blaise Pascal');
- You would then also have the new value stored in
$newSerialID for use in other queries (e.g., as a foreign key to the person table). Note that the name of the automatically created SEQUENCE object will be named <table>_<serialcolumn>_seq, where table and serialcolumn are the names of your table and your SERIAL column, respectively. -
-
+ You would then also have the new value stored in
+
$newSerialID for use in other queries (e.g., as a+ foreign key to the
person table). Note that the name+ of the automatically created SEQUENCE object will be
+ named <table>_<serialcolumn>_seq,
+ where table and serialcolumn are the names of your
+ table and your SERIAL column, respectively.
+
+
+ SERIAL value with the currval() function
+ after it was inserted by default, e.g.,
INSERT INTO person (name) VALUES ('Blaise Pascal');
$newID = currval('person_id_seq');
- Finally, you could use the
+ Finally, you could use the
+ returned from the INSERT statement to look up the
+ default value, though this is probably the least portable approach.
+ In Perl, using DBI with Edmund Mergl's DBD::Pg module, the oid
+ value is made available via $sth->{pg_oid_status} after
+ $sth->execute().
-
+
+ nextval() lead to a race condition with other users?
-
-
-
-
-
-
-
+
+ a TID?
+
+
+ Every row that is created in PostgreSQL gets a unique
+ OID. All OIDs generated during
+ initdb are less than 16384 (from
+ backend/access/transam.h). All user-created
+ OIDs are equal to or greater than this. By default,
+ all these OIDs are unique not only within a table or
+ database, but unique within the entire PostgreSQL installation.
+
+
+ tables to link rows between 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. You can create an index on the
+ OID field for faster access.
+
+
+ area that is used by all databases. If you want to change the
+ OID to something else, or if you want to make a copy
+ of the table, with the original OID's, there is no
+ reason you can't do it:
CREATE TABLE new_table(old_oid oid, mycol int);
SELECT old_oid, mycol INTO new FROM old;
-->
-
+
+ overflow at 4 billion. No one has reported this ever happening, and
+ we plan to have the limit removed before anyone does.
-
+
+ with block and offset values. Tids change after rows are modified
+ or reloaded. They are used by index entries to point to physical
+ rows.
-
+
+ terms used in PostgreSQL?
-
+
+ have more common usage. Here are some:
-
+ + "http://www.comptechnews.com/~reaster/dbdesign.html">http://www.comptechnews.com/~reaster/dbdesign.html
-
+
+ palloc failure: memory exhausted?"
-
+
+ system, or your kernel has a low limit for certain resources. Try
+ this before starting the postmaster:
ulimit -d 65536
limit datasize 64m
- Depending on your shell, only one of these may succeed, but it will set your process data segment limit much higher and perhaps allow the query to complete. This command applies to the current process, and all subprocesses created after the command is run. If you are having a problem with the SQL client because the backend is returning too much data, try it before starting the client.
-
-
+ Depending on your shell, only one of these may succeed, but it will
+ set your process data segment limit much higher and perhaps allow
+ the query to complete. This command applies to the current process,
+ and all subprocessesHTML & CSS specifications are available from http://www.w3.org/
+To learn more about Tidy see http://www.w3.org/People/Raggett/tidy/
+Please send bug reports to Dave Raggett care of
+Lobby your company to join W3C, see http://www.w3.org/Consortium
+ created after the command is run. If you are
+ having a problem with the SQL client because the
+ backend is returning too much data, try it before starting the
+ client.
+
+
+ I am running?
select version();
-
+
+ invalid large obj descriptor. Why?
-
BEGIN WORK and COMMIT around any use of a large object handle, that is, surrounding lo_open ... lo_close.+
BEGIN WORK and COMMIT+ around any use of a large object handle, that is, surrounding
+
lo_open ... lo_close.
-
+
+ handles at transaction commit. So the first attempt to do anything
+ with the handle will draw invalid large obj descriptor. So
+ code that used to work (at least most of the time) will now
+ generate that error message if you fail to use a transaction.
-
auto-commit off.+
+ may need to set
auto-commit off.
-
+
+ default to the current time?
-
IN so slow?+
+
IN so slow?
-
IN with EXISTS:+
+ scanning the result of the subquery for each row of the outer
+ query. A workaround is to replace
IN with+
EXISTS:
SELECT * FROM tab
-
+
+ example:
+
+ SELECT *
+ FROM t1 LEFT OUTER JOIN t2 USING (col);
+
+ This will join t1.col to t2.col, and return any unjoined rows in t1
+ with NULL values for t2 columns. A
+ RIGHT join would return unjoined rows of table t2. A
+ FULL join would return unjoined rows from t1 and t2.
+ The word OUTER is optional and is assumed in
+ LEFT, RIGHT, and FULL
+ joins. Ordinary joins are called INNER joins.
+
+ In previous releases, outer joins can be simulated using
+ UNION and NOT IN. For example, when
+ joining tab1 and tab2, the following query does an
+ outer join of the two tables:
+
+
SELECT tab1.col1, tab2.col2
FROM tab1, tab2
Extending PostgreSQL
-
+
+ run it in psql, why does it dump core?
-
+
+ user-defined function in a stand-alone test program first.
-
+
+ "NOTICE:PortalHeapMemoryFree: 0x402251d0 not in alloc set!"
+ mean?
-
+
+ palloc'ed. Beware of mixing malloc/free and
+ palloc/pfree.
-
+
+ types and functions to PostgreSQL?
-
+
+ and they will eventually end up in the contrib/
+ subdirectory.
-
+
+ tuple?
-
+
+ tried it, though in principle it can be done.
-
+
+ the recompile not see the change?
-
+
+ include files. You have to do a make clean and then another
+ make. If you are using GCC you can use the
+ --enable-depend option of configure to have the
+ compiler compute the dependencies automatically.