FAQ 43.9 KB
Newer Older
Bruce Momjian's avatar
Bruce Momjian committed
1 2 3

                Frequently Asked Questions (FAQ) for PostgreSQL
                                       
Bruce Momjian's avatar
Bruce Momjian committed
4
   Last updated: Fri Jun 2 11:32:13 EDT 2000
Bruce Momjian's avatar
Bruce Momjian committed
5
   
Bruce Momjian's avatar
Bruce Momjian committed
6
   Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Bruce Momjian's avatar
Bruce Momjian committed
7
   
Bruce Momjian's avatar
Bruce Momjian committed
8 9
   The most recent version of this document can be viewed at
   http://www.PostgreSQL.org/docs/faq-english.html.
Bruce Momjian's avatar
Bruce Momjian committed
10 11
   
   Linux-specific questions are answered in
12
   http://www.PostgreSQL.org/docs/faq-linux.html.
Bruce Momjian's avatar
Bruce Momjian committed
13
   
Bruce Momjian's avatar
Bruce Momjian committed
14 15 16 17
   HPUX-specific questions are answered in
   http://www.PostgreSQL.org/docs/faq-hpux.html.
   
   Solaris-specific questions are answered in
Bruce Momjian's avatar
Bruce Momjian committed
18
   http://www.PostgreSQL.org/docs/faq-solaris.html.
Bruce Momjian's avatar
Bruce Momjian committed
19
   
Bruce Momjian's avatar
Bruce Momjian committed
20
   Irix-specific questions are answered in
21
   http://www.PostgreSQL.org/docs/faq-irix.html.
Bruce Momjian's avatar
Bruce Momjian committed
22 23
     _________________________________________________________________
   
24
                             General Questions
Bruce Momjian's avatar
Bruce Momjian committed
25
                                      
Bruce Momjian's avatar
Bruce Momjian committed
26
   1.1) What is PostgreSQL?
27 28 29 30
   1.2) What's the copyright on PostgreSQL?
   1.3) What Unix platforms does PostgreSQL run on?
   1.4) What non-unix ports are available?
   1.5) Where can I get PostgreSQL?
Bruce Momjian's avatar
Bruce Momjian committed
31 32 33
   1.6) Where can I get support?
   1.7) What is the latest release?
   1.8) What documentation is available?
34 35 36 37 38 39 40 41
   1.9) How do I find out about known bugs or missing features?
   1.10) How can I learn SQL?
   1.11) Is PostgreSQL Y2K compliant?
   1.12) How do I join the development team?
   1.13) How do I submit a bug report?
   1.14) How does PostgreSQL compare to other DBMS's?
   
                           User Client Questions
Bruce Momjian's avatar
Bruce Momjian committed
42
                                      
43 44 45 46 47 48 49 50 51 52
   2.1) Are there ODBC drivers for PostgreSQL?
   2.2) What tools are available for hooking PostgreSQL to Web pages?
   2.3) Does PostgreSQL have a graphical user interface? A report
   generator? An embedded query language interface?
   2.4) What languages are available to communicate with PostgreSQL?
   
                          Administrative Questions
                                      
   3.1) Why does initdb fail?
   3.2) How do I install PostgreSQL somewhere other than
Bruce Momjian's avatar
Bruce Momjian committed
53
   /usr/local/pgsql?
54
   3.3) When I start the postmaster, I get a Bad System Call or core
Bruce Momjian's avatar
Bruce Momjian committed
55
   dumped message. Why?
Bruce Momjian's avatar
Bruce Momjian committed
56 57
   3.4) When I try to start the postmaster, I get IpcMemoryCreate errors.
   Why?
58
   3.5) When I try to start the postmaster, I get IpcSemaphoreCreate
Bruce Momjian's avatar
Bruce Momjian committed
59
   errors. Why?
60 61 62 63 64 65
   3.6) How do I prevent other hosts from accessing my PostgreSQL
   database?
   3.7) Why can't I connect to my database from another machine?
   3.8) Why can't I access the database as the root user?
   3.9) All my servers crash under concurrent table access. Why?
   3.10) How do I tune the database engine for better performance?
Bruce Momjian's avatar
Bruce Momjian committed
66 67 68
   3.11) What debugging features are available?
   3.12) I get "Sorry, too many clients" when trying to connect. Why?
   3.13) What are the pg_sorttempNNN.NN files in my database directory?
69 70
   
                           Operational Questions
Bruce Momjian's avatar
Bruce Momjian committed
71
                                      
Bruce Momjian's avatar
Bruce Momjian committed
72 73
   4.1) Why is the system confused about commas, decimal points, and date
   formats.
74
   4.2) What is the exact difference between binary cursors and normal
Bruce Momjian's avatar
Bruce Momjian committed
75
   cursors?
Bruce Momjian's avatar
Bruce Momjian committed
76 77
   4.3) How do I SELECT only the first few rows of a query?
   4.4) How do I get a list of tables or other things I can see in psql?
78 79 80
   4.5) How do you remove a column from a table?
   4.6) What is the maximum size for a row, table, database?
   4.7) How much database disk space is required to store data from a
Bruce Momjian's avatar
Bruce Momjian committed
81
   typical text file?
82 83 84 85 86 87 88
   4.8) How do I find out what indices or operations are defined in the
   database?
   4.9) My queries are slow or don't make use of the indexes. Why?
   4.10) How do I see how the query optimizer is evaluating my query?
   4.11) What is an R-tree index?
   4.12) What is Genetic Query Optimization?
   4.13) How do I do regular expression searches and case-insensitive
Bruce Momjian's avatar
Bruce Momjian committed
89
   regular expression searching?
90 91
   4.14) In a query, how do I detect if a field is NULL?
   4.15) What is the difference between the various character types?
Bruce Momjian's avatar
Bruce Momjian committed
92 93
   4.16.1) How do I create a serial/auto-incrementing field?
   4.16.2) How do I get the value of a serial insert?
Bruce Momjian's avatar
Bruce Momjian committed
94 95
   4.16.3) Don't currval() and nextval() lead to a race condition with
   other concurrent backend processes?
96 97 98
   4.17) What is an oid? What is a tid?
   4.18) What is the meaning of some of the terms used in PostgreSQL?
   4.19) Why do I get the error "FATAL: palloc failure: memory
Bruce Momjian's avatar
Bruce Momjian committed
99
   exhausted?"
100
   4.20) How do I tell what PostgreSQL version I am running?
Bruce Momjian's avatar
Bruce Momjian committed
101 102 103
   4.21) My large-object operations get invalid large obj descriptor.
   Why?
   4.22) How do I create a column that will default to the current time?
Bruce Momjian's avatar
Bruce Momjian committed
104
   4.23) Why are my subqueries using IN so slow?
Bruce Momjian's avatar
Bruce Momjian committed
105
   4.24) How do I do an outer join?
Bruce Momjian's avatar
Bruce Momjian committed
106
   
107
                            Extending PostgreSQL
Bruce Momjian's avatar
Bruce Momjian committed
108
                                      
109
   5.1) I wrote a user-defined function. When I run it in psql, why does
Bruce Momjian's avatar
Bruce Momjian committed
110
   it dump core?
111 112
   5.2) What does the message: NOTICE:PortalHeapMemoryFree: 0x402251d0
   not in alloc set! mean?
Bruce Momjian's avatar
Bruce Momjian committed
113
   5.3) How can I contribute some nifty new types and functions to
114 115 116 117
   PostgreSQL?
   5.4) How do I write a C function to return a tuple?
   5.5) I have changed a source file. Why does the recompile does not see
   the change?
Bruce Momjian's avatar
Bruce Momjian committed
118 119
     _________________________________________________________________
   
120 121 122 123
                             General Questions
                                      
    1.1) What is PostgreSQL?
    
Bruce Momjian's avatar
Bruce Momjian committed
124 125 126 127 128 129 130 131 132
   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 being performed by a team of Internet
   developers who all subscribe to the PostgreSQL development mailing
   list. The current coordinator is Marc G. Fournier
Bruce Momjian's avatar
Bruce Momjian committed
133
   (scrappy@PostgreSQL.org). (See below on how to join). This team is now
Bruce Momjian's avatar
Bruce Momjian committed
134
   responsible for all development of PostgreSQL.
Bruce Momjian's avatar
Bruce Momjian committed
135 136 137 138 139 140 141 142 143 144 145 146 147
   
   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.
   
Bruce Momjian's avatar
Bruce Momjian committed
148 149
   It is pronounced Post-Gres-Q-L.
   
150 151
    1.2) What's the copyright on PostgreSQL?
    
Bruce Momjian's avatar
Bruce Momjian committed
152 153 154 155
   PostgreSQL is subject to the following COPYRIGHT.
   
   PostgreSQL Data Base Management System
   
Bruce Momjian's avatar
Bruce Momjian committed
156 157
   Portions copyright (c) 1996-2000, PostgreSQL, Inc Portions Copyright
   (c) 1994-6 Regents of the University of California
Bruce Momjian's avatar
Bruce Momjian committed
158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177
   
   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.
   
   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.
   
   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.
   
178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
    1.3) What Unix platforms does PostgreSQL run on?
    
   The authors have compiled and tested PostgreSQL on the following
   platforms (some of these compiles require gcc):
     * aix - IBM on AIX 3.2.5 or 4.x
     * alpha - DEC Alpha AXP on Digital Unix 2.0, 3.2, 4.0
     * BSD44_derived - OSs derived from 4.4-lite BSD (NetBSD, FreeBSD)
     * bsdi - BSD/OS 2.x, 3.x, 4.x
     * dgux - DG/UX 5.4R4.11
     * hpux - HP PA-RISC on HP-UX 9.*, 10.*
     * i386_solaris - i386 Solaris
     * irix5 - SGI MIPS on IRIX 5.3
     * linux - Intel i86 Alpha SPARC PPC M68k
     * sco - SCO 3.2v5 Unixware
     * sparc_solaris - SUN SPARC on Solaris 2.4, 2.5, 2.5.1
     * sunos4 - SUN SPARC on SunOS 4.1.3
     * svr4 - Intel x86 on Intel SVR4 and MIPS
     * ultrix4 - DEC MIPS on Ultrix 4.4
       
    1.4) What non-unix ports are available?
    
   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.
   
   The database server is now working on Windows NT using the Cygnus
Bruce Momjian's avatar
Bruce Momjian committed
208
   Unix/NT porting library. See pgsql/doc/FAQ_NT in the distribution.
209 210 211 212
   
    1.5) Where can I get PostgreSQL?
    
   The primary anonymous ftp site for PostgreSQL is
Bruce Momjian's avatar
Bruce Momjian committed
213
   ftp://ftp.PostgreSQL.org/pub. For mirror sites, see our main web site.
214
   
Bruce Momjian's avatar
Bruce Momjian committed
215
    1.6) Where can I get support?
216
    
Bruce Momjian's avatar
Bruce Momjian committed
217 218
   There is no official support for PostgreSQL from the University of
   California, Berkeley. It is maintained through volunteer effort.
Bruce Momjian's avatar
Bruce Momjian committed
219
   
Bruce Momjian's avatar
Bruce Momjian committed
220
   The main mailing list is: pgsql-general@PostgreSQL.org. It is
Bruce Momjian's avatar
Bruce Momjian committed
221 222 223
   available for discussion of matters pertaining to PostgreSQL. To
   subscribe, send a mail with the lines in the body (not the subject
   line)
Bruce Momjian's avatar
Bruce Momjian committed
224 225
        subscribe
        end
Bruce Momjian's avatar
Bruce Momjian committed
226

Bruce Momjian's avatar
Bruce Momjian committed
227
   to pgsql-general-request@PostgreSQL.org.
Bruce Momjian's avatar
Bruce Momjian committed
228 229
   
   There is also a digest list available. To subscribe to this list, send
Bruce Momjian's avatar
Bruce Momjian committed
230
   email to: pgsql-general-digest-request@PostgreSQL.org with a body of:
Bruce Momjian's avatar
Bruce Momjian committed
231 232
        subscribe
        end
Bruce Momjian's avatar
Bruce Momjian committed
233 234 235 236

   Digests are sent out to members of this list whenever the main list
   has received around 30k of messages.
   
Bruce Momjian's avatar
Bruce Momjian committed
237
   The bugs mailing list is available. To subscribe to this list, send
Bruce Momjian's avatar
Bruce Momjian committed
238
   email to bugs-request@PostgreSQL.org with a body of:
Bruce Momjian's avatar
Bruce Momjian committed
239
   
Bruce Momjian's avatar
Bruce Momjian committed
240 241 242
        subscribe
        end

Bruce Momjian's avatar
Bruce Momjian committed
243
   There is also a developers discussion mailing list available. To
Bruce Momjian's avatar
Bruce Momjian committed
244
   subscribe to this list, send email to hackers-request@PostgreSQL.org
Bruce Momjian's avatar
Bruce Momjian committed
245
   with a body of:
Bruce Momjian's avatar
Bruce Momjian committed
246
   
Bruce Momjian's avatar
Bruce Momjian committed
247 248
        subscribe
        end
Bruce Momjian's avatar
Bruce Momjian committed
249

Bruce Momjian's avatar
Bruce Momjian committed
250 251
   Additional mailing lists and information about PostgreSQL can be found
   via the PostgreSQL WWW home page at:
Bruce Momjian's avatar
Bruce Momjian committed
252
   
Bruce Momjian's avatar
Bruce Momjian committed
253
     http://www.PostgreSQL.org
Bruce Momjian's avatar
Bruce Momjian committed
254
     
Bruce Momjian's avatar
Bruce Momjian committed
255
   There is also an IRC channel on EFNet, channel #PostgreSQL. I use the
Bruce Momjian's avatar
Bruce Momjian committed
256
   unix command irc -c '#PostgreSQL' "$USER" irc.phoenix.net.
Bruce Momjian's avatar
Bruce Momjian committed
257
   
258
   Commercial support for PostgreSQL is available at
Bruce Momjian's avatar
Bruce Momjian committed
259
   http://www.pgsql.com/.
260
   
Bruce Momjian's avatar
Bruce Momjian committed
261
    1.7) What is the latest release?
262
    
Bruce Momjian's avatar
Bruce Momjian committed
263
   The latest release of PostgreSQL is version 7.0.2.
Bruce Momjian's avatar
Bruce Momjian committed
264
   
Bruce Momjian's avatar
Bruce Momjian committed
265
   We plan to have major releases every four months.
Bruce Momjian's avatar
Bruce Momjian committed
266
   
Bruce Momjian's avatar
Bruce Momjian committed
267
    1.8) What documentation is available?
268
    
Bruce Momjian's avatar
Bruce Momjian committed
269
   Several manuals, manual pages, and some small test examples are
Bruce Momjian's avatar
Bruce Momjian committed
270
   included in the distribution. See the /doc directory. You can also
Bruce Momjian's avatar
Bruce Momjian committed
271
   browse the manual on-line at http://www.PostgreSQL.org/docs/postgres.
Bruce Momjian's avatar
Bruce Momjian committed
272
   
Bruce Momjian's avatar
Bruce Momjian committed
273 274
   There is a PostgreSQL book available at
   http://www.PostgreSQL.org/docs/awbook.html.
Bruce Momjian's avatar
Bruce Momjian committed
275 276 277
   
   psql has some nice \d commands to show information about types,
   operators, functions, aggregates, etc.
Bruce Momjian's avatar
Bruce Momjian committed
278
   
Bruce Momjian's avatar
Bruce Momjian committed
279
   Our web site contains even more documentation.
280 281 282 283 284 285 286 287
   
    1.9) How do I find out about known bugs or missing features?
    
   PostgreSQL supports an extended subset of SQL-92. See our TODO for a
   list of known bugs, missing features, and future plans.
   
    1.10) How can I learn SQL?
    
Bruce Momjian's avatar
Bruce Momjian committed
288
   The PostgreSQL book at http://www.PostgreSQL.org/docs/awbook.html
Bruce Momjian's avatar
Bruce Momjian committed
289 290 291
   teaches SQL. There is a nice tutorial at
   http://w3.one.net/~jhoffman/sqltut.htm and at
   http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM.
Bruce Momjian's avatar
Bruce Momjian committed
292 293 294
   
   Another one is "Teach Yourself SQL in 21 Days, Second Edition" at
   http://members.tripod.com/er4ebus/sql/index.htm 
295 296
   
   Many of our users like The Practical SQL Handbook, Bowman et al.,
Bruce Momjian's avatar
Bruce Momjian committed
297 298
   Addison Wesley. Others like The Complete Reference SQL, Groff et al.,
   McGraw-Hill.
299 300 301 302
   
    1.11) Is PostgreSQL Y2K compliant?
    
   Yes, we easily handle dates past the year 2000AD, and before 2000BC.
Bruce Momjian's avatar
Bruce Momjian committed
303
   
304 305 306 307 308 309
    1.12) How do I join the development team?
    
   First, download the latest sources 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.
Bruce Momjian's avatar
Bruce Momjian committed
310
   
Bruce Momjian's avatar
Bruce Momjian committed
311
   There are about a dozen people who have commit privileges to the
Bruce Momjian's avatar
Bruce Momjian committed
312 313 314 315
   PostgreSQL CVS archive. They each have submitted so many high-quality
   patches that it was a pain for the existing committers to keep up, and
   we had confidence that patches they committed were likely to be of
   high quality.
Bruce Momjian's avatar
Bruce Momjian committed
316
   
317 318
    1.13) How do I submit a bug report?
    
Bruce Momjian's avatar
Bruce Momjian committed
319
   Fill out the "bug-template" file and send it to: bugs@PostgreSQL.org
Bruce Momjian's avatar
Bruce Momjian committed
320
   
Bruce Momjian's avatar
Bruce Momjian committed
321
   Also check out our ftp site ftp://ftp.PostgreSQL.org/pub to see if
322 323 324 325 326 327 328 329 330
   there is a more recent PostgreSQL version or patches.
   
    1.14) How does PostgreSQL compare to other DBMS's?
    
   There are several ways of measuring software: features, performance,
   reliability, support, and price.
   
   Features
          PostgreSQL has most features present in large commercial
Bruce Momjian's avatar
Bruce Momjian committed
331 332 333 334 335
          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. We don't have outer joins, but are
336 337 338 339 340
          working on them for our next release.
          
   Performance
          PostgreSQL runs in two modes. Normal fsync mode flushes every
          completed transaction to disk, guaranteeing that if the OS
Bruce Momjian's avatar
Bruce Momjian committed
341
          crashes or loses power in the next few seconds, all your data
342 343 344 345 346 347
          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
Bruce Momjian's avatar
Bruce Momjian committed
348
          less performance overhead than full fsync mode, and will allow
Bruce Momjian's avatar
Bruce Momjian committed
349
          data integrity within 30 seconds of an OS crash.
350
          In comparison to MySQL or leaner database systems, we are
Bruce Momjian's avatar
Bruce Momjian committed
351 352 353 354
          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
Bruce Momjian's avatar
Bruce Momjian committed
355 356 357
          profiling and source code analysis. There is an interesting web
          page comparing PostgreSQL to MySQL at
          http://openacs.org/why-not-mysql.html
Bruce Momjian's avatar
Bruce Momjian committed
358 359 360 361
          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.
362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385
          
   Reliability
          We realize that a DBMS must be reliable, or it 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.
          
   Support
          Our mailing list provides a large group of developers and 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.)
          
   Price
          We are free for all use, both commercial and non-commercial.
          You can add our code to your product with no limitations,
          except those outlined in our BSD-style license stated above.
     _________________________________________________________________
Bruce Momjian's avatar
Bruce Momjian committed
386
   
387 388 389 390
                           User Client Questions
                                      
    2.1) Are there ODBC drivers for PostgreSQL?
    
Bruce Momjian's avatar
Bruce Momjian committed
391
   There are two ODBC drivers available, PsqlODBC and OpenLink ODBC.
Bruce Momjian's avatar
Bruce Momjian committed
392
   
Bruce Momjian's avatar
Bruce Momjian committed
393
   PsqlODBC is included in the distribution. More information about it
Bruce Momjian's avatar
Bruce Momjian committed
394
   can be gotten from ftp://ftp.PostgreSQL.org/pub/odbc/.
Bruce Momjian's avatar
Bruce Momjian committed
395
   
Bruce Momjian's avatar
Bruce Momjian committed
396 397 398 399 400 401
   OpenLink ODBC can be gotten from 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).
   
   They will probably be selling this product to people who need
Bruce Momjian's avatar
Bruce Momjian committed
402 403 404
   commercial-quality support, but a freeware version will always be
   available. Questions to postgres95@openlink.co.uk.
   
Bruce Momjian's avatar
Bruce Momjian committed
405 406
   See also the ODBC chapter of the Programmer's Guide.
   
407 408
    2.2) What tools are available for hooking PostgreSQL to Web pages?
    
Bruce Momjian's avatar
Bruce Momjian committed
409 410 411
   A nice introduction to Database-backed Web pages can be seen at:
   http://www.webtools.com
   
412 413
   There is also one at http://www.phone.net/home/mwm/hotlist/.
   
Bruce Momjian's avatar
Bruce Momjian committed
414
   For web integration, PHP is an excellent interface. It is at
415
   http://www.php.net
Bruce Momjian's avatar
Bruce Momjian committed
416
   
417 418
   PHP is great for simple stuff, but for more complex cases, many use
   the perl interface and CGI.pm.
Bruce Momjian's avatar
Bruce Momjian committed
419
   
420
   A WWW gateway based on WDB using perl can be downloaded from
Bruce Momjian's avatar
Bruce Momjian committed
421 422
   http://www.eol.ists.ca/~dunlop/wdb-p95
   
423 424 425
    2.3) Does PostgreSQL have a graphical user interface? A report generator?
    An embedded query language interface?
    
Bruce Momjian's avatar
Bruce Momjian committed
426
   We have a nice graphical user interface called pgaccess, which is
Bruce Momjian's avatar
Bruce Momjian committed
427
   shipped as part of the distribution. Pgaccess also has a report
428
   generator. The web page is http://www.flex.ro/pgaccess
Bruce Momjian's avatar
Bruce Momjian committed
429
   
430 431
   We also include ecpg, which is an embedded SQL query language
   interface for C.
Bruce Momjian's avatar
Bruce Momjian committed
432
   
433 434
    2.4) What languages are available to communicate with PostgreSQL?
    
Bruce Momjian's avatar
Bruce Momjian committed
435
   We have:
436 437 438 439 440 441 442 443
     * C(libpq)
     * C++(libpq++)
     * Embedded C(ecpg)
     * Java(jdbc)
     * Perl(perl5)
     * ODBC(odbc)
     * Python(PyGreSQL)
     * TCL(libpgtcl)
Bruce Momjian's avatar
Bruce Momjian committed
444
     * C Easy API(libpgeasy)
445
     * Embedded HTML(PHP from http://www.php.net)
Bruce Momjian's avatar
Bruce Momjian committed
446 447
     _________________________________________________________________
   
448 449 450 451
                          Administrative Questions
                                      
    3.1) Why does initdb fail?
    
Bruce Momjian's avatar
Bruce Momjian committed
452
   Try these:
Bruce Momjian's avatar
Bruce Momjian committed
453
     * check that you don't have any of the previous version's binaries
Bruce Momjian's avatar
Bruce Momjian committed
454
       in your path
Bruce Momjian's avatar
Bruce Momjian committed
455
     * check to see that you have the proper paths set
Bruce Momjian's avatar
Bruce Momjian committed
456
     * check that the postgres user owns the proper files
Bruce Momjian's avatar
Bruce Momjian committed
457
       
458 459
    3.2) How do I install PostgreSQL somewhere other than /usr/local/pgsql?
    
Bruce Momjian's avatar
Bruce Momjian committed
460 461 462 463
   The simplest way is to specify the --prefix option when running
   configure. If you forgot to do that, you can edit Makefile.global and
   change POSTGRESDIR accordingly, or create a Makefile.custom and define
   POSTGRESDIR there.
Bruce Momjian's avatar
Bruce Momjian committed
464
   
465 466 467
    3.3) When I start the postmaster, I get a Bad System Call or core dumped
    message. Why?
    
Bruce Momjian's avatar
Bruce Momjian committed
468
   It could be a variety of problems, but first check to see that you
Bruce Momjian's avatar
Bruce Momjian committed
469
   have System V extensions installed in your kernel. PostgreSQL requires
Bruce Momjian's avatar
Bruce Momjian committed
470
   kernel support for shared memory and semaphores.
Bruce Momjian's avatar
Bruce Momjian committed
471
   
472 473
    3.4) When I try to start the postmaster, I get IpcMemoryCreate errors. Why?
    
Bruce Momjian's avatar
Bruce Momjian committed
474 475 476 477 478 479
   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 postmaster to run
   with. For most systems, with default numbers of buffers and processes,
   you need a minimum of ~1MB.
Bruce Momjian's avatar
Bruce Momjian committed
480
   
481 482 483 484 485 486 487 488 489 490 491 492 493
    3.5) When I try to start the postmaster, I get IpcSemaphoreCreate errors.
    Why?
    
   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.
Bruce Momjian's avatar
Bruce Momjian committed
494
   
495 496
    3.6) How do I prevent other hosts from accessing my PostgreSQL database?
    
Bruce Momjian's avatar
Bruce Momjian committed
497
   By default, PostgreSQL only allows connections from the local machine
Bruce Momjian's avatar
Bruce Momjian committed
498
   using Unix domain sockets. Other machines will not be able to connect
Bruce Momjian's avatar
Bruce Momjian committed
499 500
   unless you add the -i flag to the postmaster, and enable host-based
   authentication by modifying the file $PGDATA/pg_hba.conf accordingly.
501
   This will allow TCP/IP connections.
Bruce Momjian's avatar
Bruce Momjian committed
502
   
503 504 505 506 507
    3.7) Why can't I connect to my database from another machine?
    
   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
Bruce Momjian's avatar
Bruce Momjian committed
508
   host entry to the file pgsql/data/pg_hba.conf.
509 510 511
   
    3.8) Why can't I access the database as the root user?
    
Bruce Momjian's avatar
Bruce Momjian committed
512
   You should not create database users with user id 0 (root). They will
Bruce Momjian's avatar
Bruce Momjian committed
513 514 515 516
   be unable to access the database. This is a security precaution
   because of the ability of any user to dynamically link object modules
   into the database engine.
   
517 518
    3.9) All my servers crash under concurrent table access. Why?
    
Bruce Momjian's avatar
Bruce Momjian committed
519 520 521
   This problem can be caused by a kernel that is not configured to
   support semaphores.
   
522 523
    3.10) How do I tune the database engine for better performance?
    
Bruce Momjian's avatar
Bruce Momjian committed
524
   Certainly, indices can speed up queries. The EXPLAIN command allows
Bruce Momjian's avatar
Bruce Momjian committed
525 526 527
   you to see how PostgreSQL is interpreting your query, and which
   indices are being used.
   
Bruce Momjian's avatar
Bruce Momjian committed
528
   If you are doing a lot of INSERTs, consider doing them in a large
Bruce Momjian's avatar
Bruce Momjian committed
529 530 531 532 533
   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
Bruce Momjian's avatar
Bruce Momjian committed
534
   recreating indices when making large data changes.
Bruce Momjian's avatar
Bruce Momjian committed
535 536
   
   There are several tuning things that can be done. You can disable
Bruce Momjian's avatar
Bruce Momjian committed
537
   fsync() by starting the postmaster with a -o -F option. This will
Bruce Momjian's avatar
Bruce Momjian committed
538
   prevent fsync()'s from flushing to disk after every transaction.
Bruce Momjian's avatar
Bruce Momjian committed
539 540
   
   You can also use the postmaster -B option to increase the number of
Bruce Momjian's avatar
Bruce Momjian committed
541
   shared memory buffers used by the backend processes. If you make this
Bruce Momjian's avatar
Bruce Momjian committed
542
   parameter too high, the postmaster may not start because you've
Bruce Momjian's avatar
Bruce Momjian committed
543 544
   exceeded your kernel's limit on shared memory space. Each buffer is 8K
   and the default is 64 buffers.
Bruce Momjian's avatar
Bruce Momjian committed
545
   
Bruce Momjian's avatar
Bruce Momjian committed
546
   You can also use the backend -S option to increase the maximum amount
Bruce Momjian's avatar
Bruce Momjian committed
547 548
   of memory used by the backend process for temporary sorts. The -S
   value is measured in kilobytes, and the default is 512 (ie, 512K).
Bruce Momjian's avatar
Bruce Momjian committed
549
   
Bruce Momjian's avatar
Bruce Momjian committed
550 551
   You can also use the CLUSTER command to group data in tables to match
   an index. See the cluster(l) manual page for more details.
Bruce Momjian's avatar
Bruce Momjian committed
552
   
Bruce Momjian's avatar
Bruce Momjian committed
553
    3.11) What debugging features are available?
554
    
Bruce Momjian's avatar
Bruce Momjian committed
555 556 557
   PostgreSQL has several features that report status information that
   can be valuable for debugging purposes.
   
Bruce Momjian's avatar
Bruce Momjian committed
558
   First, by running configure with the --enable-cassert option, many
Bruce Momjian's avatar
Bruce Momjian committed
559 560 561 562 563 564
   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:
Bruce Momjian's avatar
Bruce Momjian committed
565
        cd /usr/local/pgsql
Bruce Momjian's avatar
Bruce Momjian committed
566 567 568
        ./bin/postmaster >server.log 2>&1 &

   This will put a server.log file in the top-level PostgreSQL directory.
Bruce Momjian's avatar
Bruce Momjian committed
569
   This file contains useful information about problems or errors
Bruce Momjian's avatar
Bruce Momjian committed
570 571
   encountered by the server. Postmaster has a -d option that allows even
   more detailed information to be reported. The -d option takes a number
Bruce Momjian's avatar
Bruce Momjian committed
572
   that specifies the debug level. Be warned that high debug level values
Bruce Momjian's avatar
Bruce Momjian committed
573
   generate large log files.
Bruce Momjian's avatar
Bruce Momjian committed
574
   
Bruce Momjian's avatar
Bruce Momjian committed
575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590
   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.
Bruce Momjian's avatar
Bruce Momjian committed
591
   
Bruce Momjian's avatar
Bruce Momjian committed
592 593
   The postgres program has -s, -A, and -t options that can be very
   useful for debugging and performance measurements.
Bruce Momjian's avatar
Bruce Momjian committed
594 595 596 597
   
   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
Bruce Momjian's avatar
Bruce Momjian committed
598
   in the client's current directory.
Bruce Momjian's avatar
Bruce Momjian committed
599
   
600 601
    3.12) I get 'Sorry, too many clients' when trying to connect. Why?
    
Bruce Momjian's avatar
Bruce Momjian committed
602 603 604
   You need to increase the postmaster's limit on how many concurrent
   backend processes it can start.
   
Bruce Momjian's avatar
Bruce Momjian committed
605
   In PostgreSQL 6.5 and up, the default limit is 32 processes. You can
Bruce Momjian's avatar
Bruce Momjian committed
606
   increase it by restarting the postmaster with a suitable -N value.
Bruce Momjian's avatar
Bruce Momjian committed
607
   With the default configuration you can set -N as large as 1024. If you
Bruce Momjian's avatar
Bruce Momjian committed
608 609 610 611 612 613 614 615 616 617 618 619 620
   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
Bruce Momjian's avatar
Bruce Momjian committed
621
   that PostgreSQL has a limit on the number of allowed backend processes
Bruce Momjian's avatar
Bruce Momjian committed
622
   is so your system won't run out of resources.
Bruce Momjian's avatar
Bruce Momjian committed
623
   
Bruce Momjian's avatar
Bruce Momjian committed
624 625 626
   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.
Bruce Momjian's avatar
Bruce Momjian committed
627
   
Bruce Momjian's avatar
Bruce Momjian committed
628
    3.13) What are the pg_sorttempNNN.NN files in my database directory?
629 630
    
   They are temporary files generated by the query executor. For example,
Bruce Momjian's avatar
Bruce Momjian committed
631
   if a sort needs to be done to satisfy an ORDER BY, and the sort
632 633
   requires more space than the backend's -S parameter allows, then temp
   files are created to hold the extra data.
Bruce Momjian's avatar
Bruce Momjian committed
634
   
Bruce Momjian's avatar
Bruce Momjian committed
635 636 637
   The temp 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.
638
     _________________________________________________________________
Bruce Momjian's avatar
Bruce Momjian committed
639
   
640 641
                           Operational Questions
                                      
Bruce Momjian's avatar
Bruce Momjian committed
642
    4.1) Why is system confused about commas, decimal points, and date formats.
643
    
Bruce Momjian's avatar
Bruce Momjian committed
644 645 646 647
   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.
Bruce Momjian's avatar
Bruce Momjian committed
648
   
649 650 651
    4.2) What is the exact difference between binary cursors and normal
    cursors?
    
Bruce Momjian's avatar
Bruce Momjian committed
652
   See the DECLARE manual page for a description.
Bruce Momjian's avatar
Bruce Momjian committed
653
   
Bruce Momjian's avatar
Bruce Momjian committed
654
    4.3) How do I SELECT only the first few rows of a query?
655
    
Bruce Momjian's avatar
Bruce Momjian committed
656
   See the FETCH manual page, or use SELECT ... LIMIT....
Bruce Momjian's avatar
Bruce Momjian committed
657
   
Bruce Momjian's avatar
Bruce Momjian committed
658 659 660 661 662
   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.
Bruce Momjian's avatar
Bruce Momjian committed
663
   
Bruce Momjian's avatar
Bruce Momjian committed
664
    4.4) How do I get a list of tables or other things I can see in psql?
665
    
Bruce Momjian's avatar
Bruce Momjian committed
666 667 668 669 670
   You can read the source code for psql in file
   pgsql/src/bin/psql/psql.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.
Bruce Momjian's avatar
Bruce Momjian committed
671
   
672 673
    4.5) How do you remove a column from a table?
    
Bruce Momjian's avatar
Bruce Momjian committed
674
   We do not support ALTER TABLE DROP COLUMN, but do this:
675 676 677 678 679 680 681 682
        SELECT ...  -- select all columns but the one you want to remove
        INTO TABLE new_table
        FROM old_table;
        DROP TABLE old_table;
        ALTER TABLE new_table RENAME TO old_table;

    4.6) What is the maximum size for a row, table, database?
    
Bruce Momjian's avatar
Bruce Momjian committed
683 684 685 686 687 688 689 690 691 692
   These are the limits:
Maximum size for a database?             unlimited (60GB databases exist)
Maximum size for a table?                unlimited on all operating systems
Maximum size for a row?                  8k, configurable to 32k
Maximum number of rows in a table?       unlimited
Maximum number of columns table?         unlimited
Maximum number of indexes on a table?    unlimited

   Of course, these are not actually unlimited, but limited to available
   disk space.
Bruce Momjian's avatar
Bruce Momjian committed
693
   
Bruce Momjian's avatar
Bruce Momjian committed
694 695 696
   To change the maximum row size, edit include/config.h and change
   BLCKSZ. To use attributes larger than 8K, you can also use the large
   object interface.
Bruce Momjian's avatar
Bruce Momjian committed
697
   
Bruce Momjian's avatar
Bruce Momjian committed
698
   Row length limit will be removed in 7.1.
699 700
   
    4.7)How much database disk space is required to store data from a typical
Bruce Momjian's avatar
Bruce Momjian committed
701
    text file?
702
    
Bruce Momjian's avatar
Bruce Momjian committed
703 704
   A PostgreSQL database may need six and a half times the disk space
   required to store the data in a flat file.
705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726
   
   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:
    36 bytes: each row header (approximate)
   + 8 bytes: two int fields @ 4 bytes each
   + 4 bytes: pointer on page to tuple
   ----------------------------------------
    48 bytes per row

   The data page size in PostgreSQL is 8192 bytes (8 KB), so:

   8192 bytes per page
   -------------------   =  171 rows per database page (rounded up)
     48 bytes per row

   300000 data rows
   --------------------  =  1755 database pages
      171 rows per page

1755 database pages * 8192 bytes per page  =  14,376,960 bytes (14MB)

Bruce Momjian's avatar
Bruce Momjian committed
727
   Indexes do not require as much overhead, but do contain the data that
728 729 730 731 732 733 734 735 736
   is being indexed, so they can be large also.
   
    4.8) How do I find out what indices or operations are defined in the
    database?
    
   psql has a variety of backslash commands to show such information. Use
   \? to see them.
   
   Also try the file pgsql/src/tutorial/syscat.source. It illustrates
Bruce Momjian's avatar
Bruce Momjian committed
737
   many of the SELECTs needed to get information from the database system
738
   tables.
Bruce Momjian's avatar
Bruce Momjian committed
739
   
740 741
    4.9) My queries are slow or don't make use of the indexes. Why?
    
Bruce Momjian's avatar
Bruce Momjian committed
742 743 744 745 746 747
   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.
Bruce Momjian's avatar
Bruce Momjian committed
748
   
Bruce Momjian's avatar
Bruce Momjian committed
749 750
   For column-specific optimization statistics, use VACUUM ANALYZE.
   VACUUM ANALYZE is important for complex multi-join queries, so the
Bruce Momjian's avatar
Bruce Momjian committed
751 752
   optimizer can estimate the number of rows returned from each table,
   and choose the proper join order. The backend does not keep track of
Bruce Momjian's avatar
Bruce Momjian committed
753
   column statistics on its own, so VACUUM ANALYZE must be run to collect
754
   them periodically.
Bruce Momjian's avatar
Bruce Momjian committed
755
   
Bruce Momjian's avatar
Bruce Momjian committed
756 757 758
   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.
Bruce Momjian's avatar
Bruce Momjian committed
759
   
760
   When using wild-card operators such as LIKE or ~, indices can only be
Bruce Momjian's avatar
Bruce Momjian committed
761
   used if the beginning of the search is anchored to the start of the
Bruce Momjian's avatar
Bruce Momjian committed
762 763
   string. So, to use indices, LIKE searches should not begin with %, and
   ~(regular expression searches) should start with ^.
Bruce Momjian's avatar
Bruce Momjian committed
764
   
765 766
    4.10) How do I see how the query optimizer is evaluating my query?
    
Bruce Momjian's avatar
Bruce Momjian committed
767
   See the EXPLAIN manual page.
768 769 770
   
    4.11) What is an R-tree index?
    
Bruce Momjian's avatar
Bruce Momjian committed
771
   An R-tree index is used for indexing spatial data. A hash index can't
772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793
   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 efficient answer queries like 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"
   
   Builtin 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 require a bit of work and we don't currently have
   any documentation on how to do it.
   
    4.12) What is Genetic Query Optimization?
    
Bruce Momjian's avatar
Bruce Momjian committed
794 795 796
   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 non-exhaustive search.
Bruce Momjian's avatar
Bruce Momjian committed
797
   
Bruce Momjian's avatar
Bruce Momjian committed
798 799
    4.13) How do I do regular expression searches and case-insensitive regular
    expression searching?
800
    
Bruce Momjian's avatar
Bruce Momjian committed
801 802 803 804 805 806
   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:
        WHERE lower(textfield) LIKE lower(pattern)

807 808 809 810 811 812
    4.14) In a query, how do I detect if a field is NULL?
    
   You test the column with IS NULL and IS NOT NULL.
   
    4.15) What is the difference between the various character types?
    
Bruce Momjian's avatar
Bruce Momjian committed
813
Type            Internal Name   Notes
Marc G. Fournier's avatar
Marc G. Fournier committed
814
--------------------------------------------------
Bruce Momjian's avatar
Bruce Momjian committed
815
"char"          char            1 character
Bruce Momjian's avatar
Bruce Momjian committed
816 817
CHAR(#)         bpchar          blank padded to the specified fixed length
VARCHAR(#)      varchar         size specifies maximum length, no padding
Bruce Momjian's avatar
Bruce Momjian committed
818
TEXT            text            length limited only by maximum row length
Bruce Momjian's avatar
Bruce Momjian committed
819
BYTEA           bytea           variable-length array of bytes
Bruce Momjian's avatar
Bruce Momjian committed
820

Bruce Momjian's avatar
Bruce Momjian committed
821 822
   You will see the internal name when examining system catalogs and in
   some error messages.
Bruce Momjian's avatar
Bruce Momjian committed
823 824
   
   The last four types above are "varlena" types (i.e. the first four
Bruce Momjian's avatar
Bruce Momjian committed
825
   bytes are the length, followed by the data). char(#) allocates the
Bruce Momjian's avatar
Bruce Momjian committed
826
   maximum number of bytes no matter how much data is stored in the
Bruce Momjian's avatar
Bruce Momjian committed
827
   field. text, varchar(#), and bytea all have variable length on the
Bruce Momjian's avatar
Bruce Momjian committed
828
   disk, and because of this, there is a small performance penalty for
Bruce Momjian's avatar
Bruce Momjian committed
829
   using them. Specifically, the penalty is for access to all columns
Bruce Momjian's avatar
Bruce Momjian committed
830 831
   after the first column of this type.
   
Bruce Momjian's avatar
Bruce Momjian committed
832 833
    4.16.1) How do I create a serial/auto-incrementing field?
    
Bruce Momjian's avatar
Bruce Momjian committed
834
   PostgreSQL supports a SERIAL data type. It auto-creates a sequence and
Bruce Momjian's avatar
Bruce Momjian committed
835
   index on the column. For example, this:
Bruce Momjian's avatar
Bruce Momjian committed
836 837 838 839 840
        CREATE TABLE person (
                id   SERIAL,
                name TEXT
        );

Bruce Momjian's avatar
Bruce Momjian committed
841
   is automatically translated into this:
Bruce Momjian's avatar
Bruce Momjian committed
842 843 844 845 846 847 848 849 850 851 852 853
        CREATE SEQUENCE person_id_seq;
        CREATE TABLE person (
                id   INT4 NOT NULL DEFAULT nextval('person_id_seq'),
                name TEXT
        );
        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.
   
Bruce Momjian's avatar
Bruce Momjian committed
854
   Numbering Rows.
Bruce Momjian's avatar
Bruce Momjian committed
855 856
   
    4.16.2) How do I get the back the generated SERIAL value after an insert?
857
    
Bruce Momjian's avatar
Bruce Momjian committed
858 859 860 861
   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 4.16.1, that might look like
   this:
Bruce Momjian's avatar
Bruce Momjian committed
862 863 864 865 866 867 868 869 870
        $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.
   
Bruce Momjian's avatar
Bruce Momjian committed
871 872
   Alternatively, you could retrieve the just-assigned SERIAL value with
   the currval() function after it was inserted by default, e.g.,
Bruce Momjian's avatar
Bruce Momjian committed
873 874 875 876 877 878 879 880 881
        INSERT INTO person (name) VALUES ('Blaise Pascal');
        $newID = currval('person_id_seq');

   Finally, you could use the oid returned from the INSERT statement to
   lookup 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().
   
Bruce Momjian's avatar
Bruce Momjian committed
882 883
    4.16.3) Don't currval() and nextval() lead to a race condition with other
    concurrent backend processes?
Bruce Momjian's avatar
Bruce Momjian committed
884
    
Bruce Momjian's avatar
Bruce Momjian committed
885
   No. This is handled by the backends.
Bruce Momjian's avatar
Bruce Momjian committed
886
   
887 888
    4.17) What is an oid? What is a tid?
    
Bruce Momjian's avatar
Bruce Momjian committed
889
   OIDs are PostgreSQL's answer to unique row ids. Every row that is
Bruce Momjian's avatar
Bruce Momjian committed
890 891 892 893 894
   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 or greater that this. By default, all
   these oids are unique not only within a table, or database, but unique
   within the entire PostgreSQL installation.
Bruce Momjian's avatar
Bruce Momjian committed
895
   
Bruce Momjian's avatar
Bruce Momjian committed
896 897
   PostgreSQL uses oids in its internal system tables to link rows
   between tables. These oids can be used to identify specific user rows
Bruce Momjian's avatar
Bruce Momjian committed
898
   and used in joins. It is recommended you use column type oid to store
Bruce Momjian's avatar
Bruce Momjian committed
899 900
   oid values. You can create an index on the oid field for faster
   access.
Bruce Momjian's avatar
Bruce Momjian committed
901
   
Bruce Momjian's avatar
Bruce Momjian committed
902 903 904 905
   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:
Bruce Momjian's avatar
Bruce Momjian committed
906
        CREATE TABLE new_table(old_oid oid, mycol int);
Bruce Momjian's avatar
Bruce Momjian committed
907
        SELECT old_oid, mycol INTO new FROM old;
Bruce Momjian's avatar
Bruce Momjian committed
908 909 910
        COPY new TO '/tmp/pgtable';
        DELETE FROM new;
        COPY new WITH OIDS FROM '/tmp/pgtable';
Bruce Momjian's avatar
Bruce Momjian committed
911

Bruce Momjian's avatar
Bruce Momjian committed
912 913 914
   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.
Bruce Momjian's avatar
Bruce Momjian committed
915
   
916 917
    4.18) What is the meaning of some of the terms used in PostgreSQL?
    
Bruce Momjian's avatar
Bruce Momjian committed
918 919
   Some of the source code and older documentation use terms that have
   more common usage. Here are some:
Bruce Momjian's avatar
Bruce Momjian committed
920
     * table, relation, class
Bruce Momjian's avatar
Bruce Momjian committed
921
     * row, record, tuple
Bruce Momjian's avatar
Bruce Momjian committed
922
     * column, field, attribute
Bruce Momjian's avatar
Bruce Momjian committed
923 924 925 926 927 928 929
     * retrieve, select
     * replace, update
     * append, insert
     * oid, serial value
     * portal, cursor
     * range variable, table name, table alias
       
930 931
    4.19) Why do I get the error "FATAL: palloc failure: memory exhausted?"
    
Bruce Momjian's avatar
Bruce Momjian committed
932 933 934 935 936 937 938 939
   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:
        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
Bruce Momjian's avatar
Bruce Momjian committed
940
   query to complete. This command applies to the current process, and
Bruce Momjian's avatar
Bruce Momjian committed
941
   all subprocesses created after the command is run. If you are having a
Bruce Momjian's avatar
Bruce Momjian committed
942 943
   problem with the SQL client because the backend is returning too much
   data, try it before starting the client.
Bruce Momjian's avatar
Bruce Momjian committed
944
   
945 946
    4.20) How do I tell what PostgreSQL version I am running?
    
Bruce Momjian's avatar
Bruce Momjian committed
947
   From psql, type select version();
Bruce Momjian's avatar
Bruce Momjian committed
948 949 950 951 952 953
   
    4.21) My large-object operations get invalid large obj descriptor. Why?
    
   You need to put BEGIN WORK and COMMIT around any use of a large object
   handle, that is, surrounding lo_open ... lo_close.
   
Bruce Momjian's avatar
Bruce Momjian committed
954 955 956 957 958
   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.
Bruce Momjian's avatar
Bruce Momjian committed
959 960 961 962 963 964
   
   If you are using a client interface like ODBC you may need to set
   auto-commit off.
   
    4.22) How do I create a column that will default to the current time?
    
Bruce Momjian's avatar
Bruce Momjian committed
965
   Use now():
Bruce Momjian's avatar
Bruce Momjian committed
966 967 968 969 970 971 972 973 974 975 976 977 978 979 980
        CREATE TABLE test (x int, modtime timestamp default now() );

    4.23) Why are my subqueries using IN so slow?
    
   Currently, we join subqueries to outer queries by sequential scanning
   the result of the subquery for each row of the outer query. A
   workaround is to replace IN with EXISTS. For example, change:
        SELECT *
        FROM tab
        WHERE col1 IN (SELECT col2 FROM TAB2)

   to:
        SELECT *
        FROM tab
        WHERE EXISTS (SELECT col2 FROM TAB2 WHERE col1 = col2)
Bruce Momjian's avatar
Bruce Momjian committed
981

Bruce Momjian's avatar
Bruce Momjian committed
982
   We hope to fix this limitation in a future release.
Bruce Momjian's avatar
Bruce Momjian committed
983 984 985 986 987 988 989 990 991 992 993 994 995 996 997
   
    4.24) How do I do an outer join?
    
   PostgreSQL does not support outer joins in the current release. They
   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
        WHERE tab1.col1 = tab2.col1
        UNION ALL
        SELECT tab1.col1, NULL
        FROM tab1
        WHERE tab1.col1 NOT IN (SELECT tab2.col1 FROM tab2)
        ORDER BY tab1.col1
Bruce Momjian's avatar
Bruce Momjian committed
998 999
     _________________________________________________________________
   
1000 1001 1002 1003 1004
                            Extending PostgreSQL
                                      
    5.1) I wrote a user-defined function. When I run it in psql, why does it
    dump core?
    
Bruce Momjian's avatar
Bruce Momjian committed
1005
   The problem could be a number of things. Try testing your user-defined
Bruce Momjian's avatar
Bruce Momjian committed
1006
   function in a stand alone test program first.
Bruce Momjian's avatar
Bruce Momjian committed
1007
   
1008 1009 1010
    5.2) What does the message: NOTICE:PortalHeapMemoryFree: 0x402251d0 not in
    alloc set! mean?
    
Bruce Momjian's avatar
Bruce Momjian committed
1011 1012
   You are pfree'ing something that was not palloc'ed. Beware of mixing
   malloc/free and palloc/pfree.
Bruce Momjian's avatar
Bruce Momjian committed
1013
   
Bruce Momjian's avatar
Bruce Momjian committed
1014
    5.3) How can I contribute some nifty new types and functions to PostgreSQL?
1015 1016 1017
    
   Send your extensions to the pgsql-hackers mailing list, and they will
   eventually end up in the contrib/ subdirectory.
Bruce Momjian's avatar
Bruce Momjian committed
1018
   
1019 1020 1021 1022
    5.4) How do I write a C function to return a tuple?
    
   This requires wizardry so extreme that the authors have never tried
   it, though in principle it can be done.
Bruce Momjian's avatar
Bruce Momjian committed
1023
   
1024 1025 1026 1027
    5.5) I have changed a source file. Why does the recompile does not see the
    change?
    
   The Makefiles do not have the proper dependencies for include files.
Bruce Momjian's avatar
Bruce Momjian committed
1028 1029
   You have to do a make clean and then another make. You have to do a
   make clean and then another make.