FAQ.html 55.5 KB
Newer Older
Bruce Momjian's avatar
Bruce Momjian committed
1 2
<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.01 transitional//EN">

Bruce Momjian's avatar
Bruce Momjian committed
3
<HTML>
Bruce Momjian's avatar
Bruce Momjian committed
4 5
  <!-- DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN" -->
  <!-- HTML -->
6

Bruce Momjian's avatar
Bruce Momjian committed
7 8 9 10 11 12
  <HEAD>
    <META name="generator" content="HTML Tidy, see www.w3.org">

    <TITLE>PostgreSQL FAQ</TITLE>
  </HEAD>

Bruce Momjian's avatar
Bruce Momjian committed
13 14
  <BODY bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000"
  alink="#0000ff">
15
    <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
Bruce Momjian's avatar
Bruce Momjian committed
16

Bruce Momjian's avatar
Bruce Momjian committed
17
    <P>Last updated: Tue Mar  5 01:28:16 EST 2002</P>
Bruce Momjian's avatar
Bruce Momjian committed
18

Bruce Momjian's avatar
Bruce Momjian committed
19 20
    <P>Current maintainer: Bruce Momjian (<A href=
    "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
Bruce Momjian's avatar
Bruce Momjian committed
21 22
    </P>

Bruce Momjian's avatar
Bruce Momjian committed
23 24 25
    <P>The most recent version of this document can be viewed at <A
    href=
    "http://www.Postgresql.org/docs/faq-english.html">http://www.PostgreSQL.org/docs/faq-english.html</A>.</P>
Bruce Momjian's avatar
Bruce Momjian committed
26

Bruce Momjian's avatar
Bruce Momjian committed
27 28
    <P>Platform-specific questions are answered at <A href=
    "http://www.PostgreSQL.org/users-lounge/docs/faq.html">http://www.PostgreSQL.org/users-lounge/docs/faq.html</A>.</P>
Bruce Momjian's avatar
Bruce Momjian committed
29 30
    <HR>

Bruce Momjian's avatar
Bruce Momjian committed
31
    <H2 align="center">General Questions</H2>
Bruce Momjian's avatar
Bruce Momjian committed
32 33
    <A href="#1.1">1.1</A>) What is PostgreSQL? How is it
    pronounced?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
34
     <A href="#1.2">1.2</A>) What is the copyright on PostgreSQL?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
35 36
     <A href="#1.3">1.3</A>) What Unix platforms does PostgreSQL run
    on?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
37
     <A href="#1.4">1.4</A>) What non-Unix ports are available?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
38 39 40 41
     <A href="#1.5">1.5</A>) Where can I get PostgreSQL?<BR>
     <A href="#1.6">1.6</A>) Where can I get support?<BR>
     <A href="#1.7">1.7</A>) What is the latest release?<BR>
     <A href="#1.8">1.8</A>) What documentation is available?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
42 43
     <A href="#1.9">1.9</A>) How do I find out about known bugs or
    missing features?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
44
     <A href="#1.10">1.10</A>) How can I learn <SMALL>SQL</SMALL>?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
45 46 47
     <A href="#1.11">1.11</A>) Is PostgreSQL Y2K compliant?<BR>
     <A href="#1.12">1.12</A>) How do I join the development team?<BR>
     <A href="#1.13">1.13</A>) How do I submit a bug report?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
48 49 50 51
     <A href="#1.14">1.14</A>) How does PostgreSQL compare to other
    <SMALL>DBMS</SMALL>s?<BR>
     <A href="#1.15">1.15</A>) How can I financially assist
    PostgreSQL?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
52 53
     

Bruce Momjian's avatar
Bruce Momjian committed
54
    <H2 align="center">User Client Questions</H2>
Bruce Momjian's avatar
Bruce Momjian committed
55 56 57 58 59 60 61 62 63
    <A href="#2.1">2.1</A>) Are there <SMALL>ODBC</SMALL> drivers for
    PostgreSQL?<BR>
     <A href="#2.2">2.2</A>) What tools are available for using
    PostgreSQL with Web pages?<BR>
     <A href="#2.3">2.3</A>) Does PostgreSQL have a graphical user
    interface? A report generator? An embedded query language
    interface?<BR>
     <A href="#2.4">2.4</A>) What languages are available to
    communicate with PostgreSQL?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
64 65
     

Bruce Momjian's avatar
Bruce Momjian committed
66
    <H2 align="center">Administrative Questions</H2>
Bruce Momjian's avatar
Bruce Momjian committed
67 68 69 70 71 72 73 74
    <A href="#3.1">3.1</A>) How do I install PostgreSQL somewhere other
    than <I>/usr/local/pgsql</I>?<BR>
     <A href="#3.2">3.2</A>) When I start <I>postmaster</I>, I get a
    <I>Bad System Call</I> or core dumped message. Why?<BR>
     <A href="#3.3">3.3</A>) When I try to start <I>postmaster</I>, I
    get <I>IpcMemoryCreate</I> errors. Why?<BR>
     <A href="#3.4">3.4</A>) When I try to start <I>postmaster</I>, I
    get <I>IpcSemaphoreCreate</I> errors. Why?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
75 76
     <A href="#3.5">3.5</A>) How do I control connections from other
    hosts?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
77
     <A href="#3.6">3.6</A>) How do I tune the database engine for
Bruce Momjian's avatar
Bruce Momjian committed
78
    better performance?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
79 80
     <A href="#3.7">3.7</A>) What debugging features are available?<BR>
     <A href="#3.8">3.8</A>) Why do I get <I>"Sorry, too many
Bruce Momjian's avatar
Bruce Momjian committed
81
    clients"</I> when trying to connect?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
82
     <A href="#3.9">3.9</A>) What are the <I>pg_sorttempNNN.NN</I>
Bruce Momjian's avatar
Bruce Momjian committed
83
    files in my database directory?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
84 85
     

Bruce Momjian's avatar
Bruce Momjian committed
86
    <H2 align="center">Operational Questions</H2>
Bruce Momjian's avatar
Bruce Momjian committed
87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104
    <A href="#4.1">4.1</A>) What is the difference between binary
    cursors and normal cursors?<BR>
     <A href="#4.2">4.2</A>) How do I <SMALL>SELECT</SMALL> only the
    first few rows of a query?<BR>
     <A href="#4.3">4.3</A>) How do I get a list of tables or other
    things I can see in <I>psql</I>?<BR>
     <A href="#4.4">4.4</A>) How do you remove a column from a
    table?<BR>
     <A href="#4.5">4.5</A>) What is the maximum size for a row, a
    table, and a database?<BR>
     <A href="#4.6">4.6</A>) How much database disk space is required
    to store data from a typical text file?<BR>
     <A href="#4.7">4.7</A>) How do I find out what tables or indexes
    are defined in the database?<BR>
     <A href="#4.8">4.8</A>) My queries are slow or don't make use of
    the indexes. Why?<BR>
     <A href="#4.9">4.9</A>) How do I see how the query optimizer is
    evaluating my query?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
105 106
     <A href="#4.10">4.10</A>) What is an R-tree index?<BR>
     <A href="#4.11">4.11</A>) What is the Genetic Query Optimizer?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
107 108 109 110 111 112 113 114 115 116 117 118 119
     <A href="#4.12">4.12</A>) How do I perform regular expression
    searches and case-insensitive regular expression searches? How do I
    use an index for case-insensitive searches?<BR>
     <A href="#4.13">4.13</A>) In a query, how do I detect if a field
    is <SMALL>NULL</SMALL>?<BR>
     <A href="#4.14">4.14</A>) What is the difference between the
    various character types?<BR>
     <A href="#4.15.1">4.15.1</A>) How do I create a
    serial/auto-incrementing field?<BR>
     <A href="#4.15.2">4.15.2</A>) How do I get the value of a
    <SMALL>SERIAL</SMALL> insert?<BR>
     <A href="#4.15.3">4.15.3</A>) Don't <I>currval()</I> and
    <I>nextval()</I> lead to a race condition with other users?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
120 121 122
     <A href="#4.15.4">4.15.4</A>) Why aren't my sequence numbers
    reused on transaction abort? Why are there gaps in the numbering of
    my sequence/SERIAL column?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
123 124 125 126 127 128 129 130 131 132 133 134 135 136
     <A href="#4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is a
    <SMALL>TID</SMALL>?<BR>
     <A href="#4.17">4.17</A>) What is the meaning of some of the terms
    used in PostgreSQL?<BR>
     <A href="#4.18">4.18</A>) Why do I get the error <I>"ERROR: Memory
    exhausted in AllocSetAlloc()"</I>?<BR>
     <A href="#4.19">4.19</A>) How do I tell what PostgreSQL version I
    am running?<BR>
     <A href="#4.20">4.20</A>) Why does my large-object operations get
    <I>"invalid large obj descriptor"</I>?<BR>
     <A href="#4.21">4.21</A>) How do I create a column that will
    default to the current time?<BR>
     <A href="#4.22">4.22</A>) Why are my subqueries using
    <CODE><SMALL>IN</SMALL></CODE> so slow?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
137
     <A href="#4.23">4.23</A>) How do I perform an outer join?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
138 139
     <A href="#4.24">4.24</A>) How do I perform queries using multiple
    databases?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
140 141
     

Bruce Momjian's avatar
Bruce Momjian committed
142
    <H2 align="center">Extending PostgreSQL</H2>
Bruce Momjian's avatar
Bruce Momjian committed
143 144 145 146 147 148 149 150
    <A href="#5.1">5.1</A>) I wrote a user-defined function. When I run
    it in <I>psql</I>, why does it dump core?<BR>
     <A href="#5.2">5.2</A>) How can I contribute some nifty new types
    and functions to PostgreSQL?<BR>
     <A href="#5.3">5.3</A>) How do I write a C function to return a
    tuple?<BR>
     <A href="#5.4">5.4</A>) I have changed a source file. Why does the
    recompile not see the change?<BR>
Bruce Momjian's avatar
Bruce Momjian committed
151 152 153
     
    <HR>

Bruce Momjian's avatar
Bruce Momjian committed
154
    <H2 align="center">General Questions</H2>
Bruce Momjian's avatar
Bruce Momjian committed
155 156 157

    <H4><A name="1.1">1.1</A>) What is PostgreSQL?</H4>

Bruce Momjian's avatar
Bruce Momjian committed
158 159
    <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>.</P>

Bruce Momjian's avatar
Bruce Momjian committed
160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188
    <P>PostgreSQL is an enhancement of the POSTGRES database management
    system, a next-generation <SMALL>DBMS</SMALL> 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 <SMALL>SQL</SMALL>. PostgreSQL is free and the
    complete source is available.</P>

    <P>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 (<A href=
    "mailto:scrappy@PostgreSQL.org">scrappy@PostgreSQL.org</A>). (See
    below on how to join). This team is now responsible for all
    development of PostgreSQL.</P>

    <P>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.</P>

    <P>The original name of the software at Berkeley was Postgres. When
    <SMALL>SQL</SMALL> functionality was added in 1995, its name was
    changed to Postgres95. The name was changed at the end of 1996 to
    PostgreSQL.</P>

    <H4><A name="1.2">1.2</A>) What is the copyright on
    PostgreSQL?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
189 190 191 192 193

    <P>PostgreSQL is subject to the following COPYRIGHT:</P>

    <P>PostgreSQL Data Base Management System</P>

Bruce Momjian's avatar
Bruce Momjian committed
194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216
    <P>Portions copyright (c) 1996-2002, PostgreSQL Global Development
    Group Portions Copyright (c) 1994-6 Regents of the University of
    California</P>

    <P>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.</P>

    <P>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.</P>

    <P>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.</P>

Bruce Momjian's avatar
Bruce Momjian committed
217 218 219
    <P>The above is the BSD license, the classic open-source license.
    It has no restrictions on how the source code may be used. We like
    it and have no intention of changing it.</P>
Bruce Momjian's avatar
Bruce Momjian committed
220

Bruce Momjian's avatar
Bruce Momjian committed
221 222 223 224 225 226 227
    <H4><A name="1.3">1.3</A>) What Unix platforms does PostgreSQL run
    on?</H4>

    <P>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.</P>
Bruce Momjian's avatar
Bruce Momjian committed
228 229 230 231 232

    <H4><A name="1.4">1.4</A>) What non-Unix ports are available?</H4>

    <P><STRONG>Client</STRONG></P>

Bruce Momjian's avatar
Bruce Momjian committed
233 234 235 236 237 238 239
    <P>It is possible to compile the <I>libpq</I> 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 <I>win31.mak</I> is included in the distribution
    for making a Win32 <I>libpq</I> library and <I>psql</I>. PostgreSQL
    also communicates with <SMALL>ODBC</SMALL> clients.</P>
Bruce Momjian's avatar
Bruce Momjian committed
240 241 242

    <P><STRONG>Server</STRONG></P>

Bruce Momjian's avatar
Bruce Momjian committed
243 244 245 246 247 248
    <P>The database server can run on Windows NT and Win2k using
    Cygwin, the Cygnus Unix/NT porting library. See
    <I>pgsql/doc/FAQ_MSWIN</I> in the distribution or the <A href=
    "http://www.postgresql.org/docs/faq-mswin.html">MS Windows FAQ</A>
    on our web site. We have no plan to do a native port to any
    Microsoft platform.</P>
249

Bruce Momjian's avatar
Bruce Momjian committed
250
    <H4><A name="1.5">1.5</A>) Where can I get PostgreSQL?</H4>
251

Bruce Momjian's avatar
Bruce Momjian committed
252 253 254
    <P>The primary anonymous ftp site for PostgreSQL is <A href=
    "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A>.
    For mirror sites, see our main web site.</P>
255

Bruce Momjian's avatar
Bruce Momjian committed
256
    <H4><A name="1.6">1.6</A>) Where can I get support?</H4>
257

Bruce Momjian's avatar
Bruce Momjian committed
258 259 260 261 262
    <P>The main mailing list is: <A href=
    "mailto:pgsql-general@PostgreSQL.org">pgsql-general@PostgreSQL.org</A>.
    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):</P>
Bruce Momjian's avatar
Bruce Momjian committed
263 264 265 266
<PRE>
    subscribe
    end
</PRE>
267

Bruce Momjian's avatar
Bruce Momjian committed
268 269
    <P>to <A href=
    "mailto:pgsql-general-request@PostgreSQL.org">pgsql-general-request@PostgreSQL.org</A>.</P>
270

Bruce Momjian's avatar
Bruce Momjian committed
271 272 273 274
    <P>There is also a digest list available. To subscribe to this
    list, send email to: <A href=
    "mailto:pgsql-general-digest-request@PostgreSQL.org">pgsql-general-digest-request@PostgreSQL.org</A>
    with a body of:</P>
Bruce Momjian's avatar
Bruce Momjian committed
275 276 277 278
<PRE>
    subscribe
    end
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
279 280
    Digests are sent out to members of this list whenever the main list
    has received around 30k of messages. 
281

Bruce Momjian's avatar
Bruce Momjian committed
282 283 284 285
    <P>The bugs mailing list is available. To subscribe to this list,
    send email to <A href=
    "mailto:pgsql-bugs-request@PostgreSQL.org">pgsql-bugs-request@PostgreSQL.org</A>
    with a body of:</P>
Bruce Momjian's avatar
Bruce Momjian committed
286 287 288 289
<PRE>
    subscribe
    end
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
290 291 292 293
    There is also a developers discussion mailing list available. To
    subscribe to this list, send email to <A href=
    "mailto:pgsql-hackers-request@PostgreSQL.org">pgsql-hackers-request@PostgreSQL.org</A>
    with a body of: 
Bruce Momjian's avatar
Bruce Momjian committed
294 295 296 297
<PRE>
    subscribe
    end
</PRE>
298

Bruce Momjian's avatar
Bruce Momjian committed
299 300
    <P>Additional mailing lists and information about PostgreSQL can be
    found via the PostgreSQL WWW home page at:</P>
301

Bruce Momjian's avatar
Bruce Momjian committed
302 303 304
    <BLOCKQUOTE>
      <A href="http://www.PostgreSQL.org">http://www.PostgreSQL.org</A>
    </BLOCKQUOTE>
305

Bruce Momjian's avatar
Bruce Momjian committed
306 307 308
    <P>There is also an IRC channel on EFNet, channel
    <I>#PostgreSQL</I>. I use the Unix command <CODE>irc -c
    '#PostgreSQL' "$USER" irc.phoenix.net.</CODE></P>
309

Bruce Momjian's avatar
Bruce Momjian committed
310 311
    <P>A list of commercial support companies is available at <A href=
    "http://www.postgresql.org/users-lounge/commercial-support.html">http://www.postgresql.org/users-lounge/commercial-support.html</A>.</P>
312

Bruce Momjian's avatar
Bruce Momjian committed
313
    <H4><A name="1.7">1.7</A>) What is the latest release?</H4>
314

Bruce Momjian's avatar
Bruce Momjian committed
315
    <P>The latest release of PostgreSQL is version 7.2.</P>
316

Bruce Momjian's avatar
Bruce Momjian committed
317
    <P>We plan to have major releases every four months.</P>
318

Bruce Momjian's avatar
Bruce Momjian committed
319
    <H4><A name="1.8">1.8</A>) What documentation is available?</H4>
320

Bruce Momjian's avatar
Bruce Momjian committed
321 322 323 324
    <P>Several manuals, manual pages, and some small test examples are
    included in the distribution. See the <I>/doc</I> directory. You
    can also browse the manual online at <A href=
    "http://www.PostgreSQL.org/users-lounge/docs/">http://www.PostgreSQL.org/users-lounge/docs/</A>.</P>
325

Bruce Momjian's avatar
Bruce Momjian committed
326 327 328 329
    <P>There are two PostgreSQL books available online at <A href=
    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
    and <A href=
    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook/</A>.
Bruce Momjian's avatar
Bruce Momjian committed
330 331
    There is a list of PostgreSQL books available for purchase at <A
    href=
Bruce Momjian's avatar
Bruce Momjian committed
332
    "http://www.postgresql.org/books/">http://www.postgresql.org/books/</A>.
Bruce Momjian's avatar
Bruce Momjian committed
333 334
    There is also a collection of PostgreSQL technical articles at <A
    href=
Bruce Momjian's avatar
Bruce Momjian committed
335
    "http://techdocs.postgresql.org/">http://techdocs.postgresql.org/</A>.</P>
336

Bruce Momjian's avatar
Bruce Momjian committed
337 338
    <P><I>psql</I> has some nice \d commands to show information about
    types, operators, functions, aggregates, etc.</P>
339

Bruce Momjian's avatar
Bruce Momjian committed
340
    <P>Our web site contains even more documentation.</P>
Bruce Momjian's avatar
Bruce Momjian committed
341

Bruce Momjian's avatar
Bruce Momjian committed
342 343
    <H4><A name="1.9">1.9</A>) How do I find out about known bugs or
    missing features?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
344

Bruce Momjian's avatar
Bruce Momjian committed
345 346 347
    <P>PostgreSQL supports an extended subset of <SMALL>SQL</SMALL>-92.
    See our <A href="http://developer.PostgreSQL.org/todo.php">TODO</A>
    list for known bugs, missing features, and future plans.</P>
348

Bruce Momjian's avatar
Bruce Momjian committed
349 350
    <H4><A name="1.10">1.10</A>) How can I learn
    <SMALL>SQL</SMALL>?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
351

Bruce Momjian's avatar
Bruce Momjian committed
352 353
    <P>The PostgreSQL book at <A href=
    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
Bruce Momjian's avatar
Bruce Momjian committed
354 355 356
    teaches <SMALL>SQL</SMALL>. There is another PostgreSQL book at <A
    href=
    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook.</A>
Bruce Momjian's avatar
Bruce Momjian committed
357 358 359
    There is a nice tutorial at <A href=
    "http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
    at <A href=
Bruce Momjian's avatar
Bruce Momjian committed
360
    "http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
Bruce Momjian's avatar
Bruce Momjian committed
361 362 363
    http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,</A>
    and at <A href=
    "http://sqlcourse.com/">http://sqlcourse.com.</A></P>
Bruce Momjian's avatar
Bruce Momjian committed
364

Bruce Momjian's avatar
Bruce Momjian committed
365 366 367
    <P>Another one is "Teach Yourself SQL in 21 Days, Second Edition"
    at <A href=
    "http://members.tripod.com/er4ebus/sql/index.htm">http://members.tripod.com/er4ebus/sql/index.htm</A></P>
Bruce Momjian's avatar
Bruce Momjian committed
368

Bruce Momjian's avatar
Bruce Momjian committed
369 370 371
    <P>Many of our users like <I>The Practical SQL Handbook</I>,
    Bowman, Judith S., et al., Addison-Wesley. Others like <I>The
    Complete Reference SQL</I>, Groff et al., McGraw-Hill.</P>
Bruce Momjian's avatar
Bruce Momjian committed
372 373 374

    <H4><A name="1.11">1.11</A>) Is PostgreSQL Y2K compliant?</H4>

Bruce Momjian's avatar
Bruce Momjian committed
375 376
    <P>Yes, we easily handle dates past the year 2000 AD, and before
    2000 BC.</P>
Bruce Momjian's avatar
Bruce Momjian committed
377

Bruce Momjian's avatar
Bruce Momjian committed
378 379
    <H4><A name="1.12">1.12</A>) How do I join the development
    team?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
380

Bruce Momjian's avatar
Bruce Momjian committed
381 382 383 384 385
    <P>First, download the latest source and read the PostgreSQL
    Developers documentation on our web site, or in the distribution.
    Second, subscribe to the <I>pgsql-hackers</I> and
    <I>pgsql-patches</I> mailing lists. Third, submit high quality
    patches to pgsql-patches.</P>
Bruce Momjian's avatar
Bruce Momjian committed
386

Bruce Momjian's avatar
Bruce Momjian committed
387 388 389 390 391
    <P>There are about a dozen people who have commit privileges to the
    PostgreSQL <SMALL>CVS</SMALL> 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.</P>
Bruce Momjian's avatar
Bruce Momjian committed
392 393 394

    <H4><A name="1.13">1.13</A>) How do I submit a bug report?</H4>

Bruce Momjian's avatar
Bruce Momjian committed
395 396 397 398
    <P>Please visit the <A href=
    "http://www.postgresql.org/bugs/bugs.php">PostgreSQL BugTool</A>
    page, which gives guidelines and directions on how to submit a
    bug.</P>
Bruce Momjian's avatar
Bruce Momjian committed
399

Bruce Momjian's avatar
Bruce Momjian committed
400 401 402
    <P>Also check out our ftp site <A href=
    "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A> to
    see if there is a more recent PostgreSQL version or patches.</P>
Bruce Momjian's avatar
Bruce Momjian committed
403

Bruce Momjian's avatar
Bruce Momjian committed
404 405
    <H4><A name="1.14">1.14</A>) How does PostgreSQL compare to other
    <SMALL>DBMS</SMALL>s?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
406

Bruce Momjian's avatar
Bruce Momjian committed
407 408
    <P>There are several ways of measuring software: features,
    performance, reliability, support, and price.</P>
Bruce Momjian's avatar
Bruce Momjian committed
409 410 411 412

    <DL>
      <DT><B>Features</B></DT>

Bruce Momjian's avatar
Bruce Momjian committed
413 414 415 416 417 418
      <DD>PostgreSQL has most features present in large commercial
      <SMALL>DBMS</SMALL>s, like transactions, subselects, triggers,
      views, foreign key referential integrity, and sophisticated
      locking. We have some features they do not have, like
      user-defined types, inheritance, rules, and multi-version
      concurrency control to reduce lock contention.<BR>
Bruce Momjian's avatar
Bruce Momjian committed
419 420 421 422 423
      <BR>
      </DD>

      <DT><B>Performance</B></DT>

Bruce Momjian's avatar
Bruce Momjian committed
424 425 426 427 428 429 430 431 432 433 434
      <DD>PostgreSQL runs in two modes. Normal <I>fsync</I> mode
      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
      <I>no-fsync</I> 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.<BR>
Bruce Momjian's avatar
Bruce Momjian committed
435
      <BR>
Bruce Momjian's avatar
Bruce Momjian committed
436 437 438 439 440 441 442 443 444
       In comparison to MySQL or leaner database systems, we are slower
      on inserts/updates because we have transaction overhead. Of
      course, MySQL does not have any of the features mentioned in the
      <I>Features</I> 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 <A href=
      "http://openacs.org/why-not-mysql.html">http://openacs.org/why-not-mysql.html</A><BR>

Bruce Momjian's avatar
Bruce Momjian committed
445
      <BR>
Bruce Momjian's avatar
Bruce Momjian committed
446 447 448 449
       We handle each user connection by creating a Unix process.
      Backend processes share data buffers and locking information.
      With multiple CPUs, multiple backends can easily run on different
      CPUs.<BR>
Bruce Momjian's avatar
Bruce Momjian committed
450 451 452 453 454
      <BR>
      </DD>

      <DT><B>Reliability</B></DT>

Bruce Momjian's avatar
Bruce Momjian committed
455 456 457 458 459 460 461
      <DD>We realize that a <SMALL>DBMS</SMALL> 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.<BR>
Bruce Momjian's avatar
Bruce Momjian committed
462 463 464 465 466
      <BR>
      </DD>

      <DT><B>Support</B></DT>

Bruce Momjian's avatar
Bruce Momjian committed
467 468 469 470 471 472 473 474
      <DD>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 <SMALL>DBMS</SMALL>s do not always
      supply a fix either. Direct access to developers, the user
      community, manuals, and the source code often make PostgreSQL
      support superior to other <SMALL>DBMS</SMALL>s. There is
      commercial per-incident support available for those who need it.
      (See <A href="#1.6">support FAQ item</A>.)<BR>
Bruce Momjian's avatar
Bruce Momjian committed
475 476 477 478 479
      <BR>
      </DD>

      <DT><B>Price</B></DT>

Bruce Momjian's avatar
Bruce Momjian committed
480 481 482
      <DD>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.<BR>
Bruce Momjian's avatar
Bruce Momjian committed
483 484 485
      <BR>
      </DD>
    </DL>
Bruce Momjian's avatar
Bruce Momjian committed
486

Bruce Momjian's avatar
Bruce Momjian committed
487 488
    <H4><A name="1.15">1.15</A>) How can I financially assist
    PostgreSQL?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
489

Bruce Momjian's avatar
Bruce Momjian committed
490 491 492
    <P>PostgreSQL has had a first-class infrastructure since we started
    six years ago. This is all thanks to Marc Fournier, who has created
    and managed this infrastructure over the years.</P>
Bruce Momjian's avatar
Bruce Momjian committed
493

Bruce Momjian's avatar
Bruce Momjian committed
494 495 496
    <P>Quality infrastructure is very important to an open-source
    project. It prevents disruptions that can greatly delay forward
    movement of the project.</P>
Bruce Momjian's avatar
Bruce Momjian committed
497

Bruce Momjian's avatar
Bruce Momjian committed
498 499 500 501 502 503
    <P>Of course, this infrastructure is not cheap. There are a variety
    of monthly and one-time expenses that are required to keep it
    going. If you or your company has money it can donate to help fund
    this effort, please go to <A href=
    "http://www.pgsql.com/pg_goodies">http://www.pgsql.com/pg_goodies</A>
    and make a donation.</P>
Bruce Momjian's avatar
Bruce Momjian committed
504

Bruce Momjian's avatar
Bruce Momjian committed
505 506 507 508
    <P>Although the web page mentions PostgreSQL, Inc, the
    "contributions" item is solely to support the PostgreSQL project
    and does not fund any specific company. If you prefer, you can also
    send a check to the contact address.</P>
Bruce Momjian's avatar
Bruce Momjian committed
509
    <HR>
510

Bruce Momjian's avatar
Bruce Momjian committed
511
    <H2 align="center">User Client Questions</H2>
512

Bruce Momjian's avatar
Bruce Momjian committed
513 514
    <H4><A name="2.1">2.1</A>) Are there <SMALL>ODBC</SMALL> drivers
    for PostgreSQL?</H4>
515

Bruce Momjian's avatar
Bruce Momjian committed
516 517
    <P>There are two <SMALL>ODBC</SMALL> drivers available, PsqlODBC
    and OpenLink <SMALL>ODBC</SMALL>.</P>
518

Bruce Momjian's avatar
Bruce Momjian committed
519 520 521
    <P>PsqlODBC is included in the distribution. More information about
    it can be gotten from <A href=
    "ftp://ftp.PostgreSQL.org/pub/odbc/">ftp://ftp.PostgreSQL.org/pub/odbc/</A>.</P>
522

Bruce Momjian's avatar
Bruce Momjian committed
523 524 525 526 527
    <P>OpenLink <SMALL>ODBC</SMALL> can be gotten from <A href=
    "http://www.openlinksw.com/">http://www.openlinksw.com</A>. It
    works with their standard <SMALL>ODBC</SMALL> client software so
    you'll have PostgreSQL <SMALL>ODBC</SMALL> available on every
    client platform they support (Win, Mac, Unix, VMS).</P>
528

Bruce Momjian's avatar
Bruce Momjian committed
529 530 531 532
    <P>They will probably be selling this product to people who need
    commercial-quality support, but a freeware version will always be
    available. Please send questions to <A href=
    "mailto:postgres95@openlink.co.uk">postgres95@openlink.co.uk</A>.</P>
533

Bruce Momjian's avatar
Bruce Momjian committed
534 535 536
    <P>See also the <A href=
    "http://www.postgresql.org/devel-corner/docs/programmer/odbc.html">ODBC
    chapter of the Programmer's Guide</A>.</P>
537

Bruce Momjian's avatar
Bruce Momjian committed
538 539
    <H4><A name="2.2">2.2</A>) What tools are available for using
    PostgreSQL with Web pages?</H4>
540

Bruce Momjian's avatar
Bruce Momjian committed
541 542
    <P>A nice introduction to Database-backed Web pages can be seen at:
    <A href="http://www.webreview.com">http://www.webreview.com</A></P>
543

Bruce Momjian's avatar
Bruce Momjian committed
544 545
    <P>There is also one at <A href=
    "http://www.phone.net/home/mwm/hotlist/">http://www.phone.net/home/mwm/hotlist/.</A></P>
546

Bruce Momjian's avatar
Bruce Momjian committed
547 548
    <P>For Web integration, PHP is an excellent interface. It is at <A
    href="http://www.php.net">http://www.php.net</A>.</P>
549

Bruce Momjian's avatar
Bruce Momjian committed
550
    <P>For complex cases, many use the Perl interface and CGI.pm.</P>
551

Bruce Momjian's avatar
Bruce Momjian committed
552 553 554
    <H4><A name="2.3">2.3</A>) Does PostgreSQL have a graphical user
    interface? A report generator? An embedded query language
    interface?</H4>
555

Bruce Momjian's avatar
Bruce Momjian committed
556 557 558 559
    <P>We have a nice graphical user interface called <I>pgaccess</I>,
    which is shipped as part of the distribution. <I>pgaccess</I> also
    has a report generator. The Web page is <A href=
    "http://www.flex.ro/pgaccess">http://www.flex.ro/pgaccess</A></P>
560

Bruce Momjian's avatar
Bruce Momjian committed
561 562
    <P>We also include <I>ecpg</I>, which is an embedded SQL query
    language interface for C.</P>
563

Bruce Momjian's avatar
Bruce Momjian committed
564 565
    <H4><A name="2.4">2.4</A>) What languages are available to
    communicate with PostgreSQL?</H4>
566

Bruce Momjian's avatar
Bruce Momjian committed
567
    <P>We have:</P>
568

Bruce Momjian's avatar
Bruce Momjian committed
569 570
    <UL>
      <LI>C (libpq)</LI>
571

Bruce Momjian's avatar
Bruce Momjian committed
572
      <LI>C++ (libpq++)</LI>
573

Bruce Momjian's avatar
Bruce Momjian committed
574
      <LI>Embedded C (ecpg)</LI>
575

Bruce Momjian's avatar
Bruce Momjian committed
576
      <LI>Java (jdbc)</LI>
577

Bruce Momjian's avatar
Bruce Momjian committed
578
      <LI>Perl (perl5)</LI>
579

Bruce Momjian's avatar
Bruce Momjian committed
580
      <LI>ODBC (odbc)</LI>
581

Bruce Momjian's avatar
Bruce Momjian committed
582
      <LI>Python (PyGreSQL)</LI>
583

Bruce Momjian's avatar
Bruce Momjian committed
584
      <LI>TCL (libpgtcl)</LI>
585

Bruce Momjian's avatar
Bruce Momjian committed
586
      <LI>C Easy API (libpgeasy)</LI>
587

Bruce Momjian's avatar
Bruce Momjian committed
588 589
      <LI>Embedded <SMALL>HTML</SMALL> (<A href=
      "http://www.php.net">PHP from http://www.php.net</A>)</LI>
Bruce Momjian's avatar
Bruce Momjian committed
590 591
    </UL>
    <HR>
592

Bruce Momjian's avatar
Bruce Momjian committed
593 594
    <H2 align="center">Administrative Questions</H2>

Bruce Momjian's avatar
Bruce Momjian committed
595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641
    <H4><A name="3.1">3.1</A>) How do I install PostgreSQL somewhere
    other than <I>/usr/local/pgsql</I>?</H4>

    <P>Specify the <I>--prefix</I> option when running
    <I>configure</I>.</P>

    <H4><A name="3.2">3.2</A>) When I start <I>postmaster</I>, I get a
    <I>Bad System Call</I> or core dumped message. Why?</H4>

    <P>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.</P>

    <H4><A name="3.3">3.3</A>) When I try to start <I>postmaster</I>, I
    get <I>IpcMemoryCreate</I> errors. Why?</H4>

    <P>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
    <I>postmaster</I>. For most systems, with default numbers of
    buffers and processes, you need a minimum of ~1 MB. See the <A
    href=
    "http://www.postgresql.org/idocs/index.php?kernel-resources.html">PostgreSQL
    Administrator's Guide</A> for more detailed information about
    shared memory and semaphores.</P>

    <H4><A name="3.4">3.4</A>) When I try to start <I>postmaster</I>, I
    get <I>IpcSemaphoreCreate</I> errors. Why?</H4>

    <P>If the error message is <I>IpcSemaphoreCreate: semget failed (No
    space left on device)</I> then your kernel is not configured with
    enough semaphores. Postgres needs one semaphore per potential
    backend process. A temporary solution is to start <I>postmaster</I>
    with a smaller limit on the number of backend processes. Use
    <I>-N</I> with a parameter less than the default of 32. A more
    permanent solution is to increase your kernel's
    <SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI</SMALL> parameters.</P>

    <P>Inoperative semaphores can also cause crashes during heavy
    database access.</P>

    <P>If the error message is something else, you might not have
    semaphore support configured in your kernel at all. See the
    PostgreSQL Administrator's Guide for more detailed information
    about shared memory and semaphores.</P>

Bruce Momjian's avatar
Bruce Momjian committed
642 643
    <H4><A name="3.5">3.5</A>) How do I control connections from other
    hosts?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
644 645 646 647 648 649 650 651

    <P>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>-i</I> flag to <I>postmaster</I>,
    <B>and</B> enable host-based authentication by modifying the file
    <I>$PGDATA/pg_hba.conf</I> accordingly. This will allow TCP/IP
    connections.</P>

Bruce Momjian's avatar
Bruce Momjian committed
652
    <H4><A name="3.6">3.6</A>) How do I tune the database engine for
Bruce Momjian's avatar
Bruce Momjian committed
653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688
    better performance?</H4>

    <P>Certainly, indexes can speed up queries. The
    <SMALL>EXPLAIN</SMALL> command allows you to see how PostgreSQL is
    interpreting your query, and which indexes are being used.</P>

    <P>If you are doing many <SMALL>INSERTs</SMALL>, consider doing
    them in a large batch using the <SMALL>COPY</SMALL> command. This
    is much faster than individual <SMALL>INSERTS.</SMALL> Second,
    statements not in a <SMALL>BEGIN WORK/COMMIT</SMALL> 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 indexes when making large data changes.</P>

    <P>There are several tuning options. You can disable <I>fsync()</I>
    by starting <I>postmaster</I> with a <I>-o -F</I> option. This will
    prevent <I>fsync()</I>s from flushing to disk after every
    transaction.</P>

    <P>You can also use the <I>postmaster</I> <I>-B</I> option to
    increase the number of shared memory buffers used by the backend
    processes. If you make this parameter too high, the
    <I>postmaster</I> may not start because you have exceeded your
    kernel's limit on shared memory space. Each buffer is 8K and the
    default is 64 buffers.</P>

    <P>You can also use the backend <I>-S</I> option to increase the
    maximum amount of memory used by the backend process for temporary
    sorts. The <I>-S</I> value is measured in kilobytes, and the
    default is 512 (i.e. 512K).</P>

    <P>You can also use the <SMALL>CLUSTER</SMALL> command to group
    data in tables to match an index. See the <SMALL>CLUSTER</SMALL>
    manual page for more details.</P>

Bruce Momjian's avatar
Bruce Momjian committed
689
    <H4><A name="3.7">3.7</A>) What debugging features are
Bruce Momjian's avatar
Bruce Momjian committed
690 691 692 693 694 695 696 697 698 699 700 701 702
    available?</H4>

    <P>PostgreSQL has several features that report status information
    that can be valuable for debugging purposes.</P>

    <P>First, by running <I>configure</I> with the --enable-cassert
    option, many <I>assert()</I>s monitor the progress of the backend
    and halt the program when something unexpected occurs.</P>

    <P>Both <I>postmaster</I> and <I>postgres</I> have several debug
    options available. First, whenever you start <I>postmaster</I>,
    make sure you send the standard output and error to a log file,
    like:</P>
703
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
704 705 706
    cd /usr/local/pgsql
    ./bin/postmaster &gt;server.log 2&gt;&amp;1 &amp;
</PRE>
707

Bruce Momjian's avatar
Bruce Momjian committed
708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744
    <P>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. <I>Postmaster</I> has a <I>-d</I>
    option that allows even more detailed information to be reported.
    The <I>-d</I> option takes a number that specifies the debug level.
    Be warned that high debug level values generate large log
    files.</P>

    <P>If <I>postmaster</I> is not running, you can actually run the
    <I>postgres</I> backend from the command line, and type your
    <SMALL>SQL</SMALL> statement directly. This is recommended
    <B>only</B> 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 <I>postmaster</I>, it is not
    running in an identical environment and locking/backend interaction
    problems may not be duplicated.</P>

    <P>If <I>postmaster</I> is running, start <I>psql</I> in one
    window, then find the <SMALL>PID</SMALL> of the <I>postgres</I>
    process used by <I>psql</I>. Use a debugger to attach to the
    <I>postgres</I> <SMALL>PID.</SMALL> You can set breakpoints in the
    debugger and issue queries from <I>psql</I>. If you are debugging
    <I>postgres</I> startup, you can set PGOPTIONS="-W n", then start
    <I>psql</I>. This will cause startup to delay for <I>n</I> seconds
    so you can attach to the process with the debugger, set any
    breakpoints, and continue through the startup sequence.</P>

    <P>The <I>postgres</I> program has <I>-s, -A</I>, and <I>-t</I>
    options that can be very useful for debugging and performance
    measurements.</P>

    <P>You can also compile with profiling to see what functions are
    taking execution time. The backend profile files will be deposited
    in the <I>pgsql/data/base/dbname</I> directory. The client profile
    file will be put in the client's current directory.</P>

Bruce Momjian's avatar
Bruce Momjian committed
745
    <H4><A name="3.8">3.8</A>) Why do I get <I>"Sorry, too many
Bruce Momjian's avatar
Bruce Momjian committed
746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774
    clients"</I> when trying to connect?</H4>

    <P>You need to increase <I>postmaster</I>'s limit on how many
    concurrent backend processes it can start.</P>

    <P>The default limit is 32 processes. You can increase it by
    restarting <I>postmaster</I> with a suitable <I>-N</I> value or
    modifying <I>postgresql.conf</I>.</P>

    <P>Note that if you make <I>-N</I> larger than 32, you must also
    increase <I>-B</I> beyond its default of 64; <I>-B</I> must be at
    least twice <I>-N</I>, 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, <SMALL>SHMMAX;</SMALL> the maximum number
    of semaphores, <SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI;</SMALL> the
    maximum number of processes, <SMALL>NPROC;</SMALL> the maximum
    number of processes per user, <SMALL>MAXUPRC;</SMALL> and the
    maximum number of open files, <SMALL>NFILE</SMALL> and
    <SMALL>NINODE.</SMALL> The reason that PostgreSQL has a limit on
    the number of allowed backend processes is so your system won't run
    out of resources.</P>

    <P>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
    <I>include/storage/sinvaladt.h</I>.</P>

Bruce Momjian's avatar
Bruce Momjian committed
775
    <H4><A name="3.9">3.9</A>) What are the <I>pg_sorttempNNN.NN</I>
Bruce Momjian's avatar
Bruce Momjian committed
776 777 778 779 780 781 782 783 784 785 786 787
    files in my database directory?</H4>

    <P>They are temporary files generated by the query executor. For
    example, if a sort needs to be done to satisfy an <SMALL>ORDER
    BY,</SMALL> and the sort requires more space than the backend's
    <I>-S</I> parameter allows, then temporary files are created to
    hold the extra data.</P>

    <P>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.</P>
Bruce Momjian's avatar
Bruce Momjian committed
788 789
    <HR>

Bruce Momjian's avatar
Bruce Momjian committed
790
    <H2 align="center">Operational Questions</H2>
Bruce Momjian's avatar
Bruce Momjian committed
791

Bruce Momjian's avatar
Bruce Momjian committed
792 793
    <H4><A name="4.1">4.1</A>) What is the difference between binary
    cursors and normal cursors?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
794

Bruce Momjian's avatar
Bruce Momjian committed
795 796
    <P>See the <SMALL>DECLARE</SMALL> manual page for a
    description.</P>
Bruce Momjian's avatar
Bruce Momjian committed
797

Bruce Momjian's avatar
Bruce Momjian committed
798 799
    <H4><A name="4.2">4.2</A>) How do I <SMALL>SELECT</SMALL> only the
    first few rows of a query?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
800

Bruce Momjian's avatar
Bruce Momjian committed
801 802
    <P>See the <SMALL>FETCH</SMALL> manual page, or use
    <SMALL>SELECT</SMALL> ... <SMALL>LIMIT</SMALL>....</P>
Bruce Momjian's avatar
Bruce Momjian committed
803

Bruce Momjian's avatar
Bruce Momjian committed
804 805 806 807 808 809
    <P>The entire query may have to be evaluated, even if you only want
    the first few rows. Consider a query that has an <SMALL>ORDER
    BY.</SMALL> If there is an index that matches the <SMALL>ORDER
    BY</SMALL>, 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.</P>
Bruce Momjian's avatar
Bruce Momjian committed
810

Bruce Momjian's avatar
Bruce Momjian committed
811 812
    <H4><A name="4.3">4.3</A>) How do I get a list of tables or other
    things I can see in <I>psql</I>?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
813

Bruce Momjian's avatar
Bruce Momjian committed
814 815 816 817 818 819
    <P>You can read the source code for <I>psql</I> in file
    <I>pgsql/src/bin/psql/describe.c</I>. It contains
    <SMALL>SQL</SMALL> commands that generate the output for psql's
    backslash commands. You can also start <I>psql</I> with the
    <I>-E</I> option so it will print out the queries it uses to
    execute the commands you give.</P>
Bruce Momjian's avatar
Bruce Momjian committed
820

Bruce Momjian's avatar
Bruce Momjian committed
821 822
    <H4><A name="4.4">4.4</A>) How do you remove a column from a
    table?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
823

Bruce Momjian's avatar
Bruce Momjian committed
824 825
    <P>We do not support <SMALL>ALTER TABLE DROP COLUMN,</SMALL> but do
    this:</P>
826
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
827 828 829 830 831 832
    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;
</PRE>
833

Bruce Momjian's avatar
Bruce Momjian committed
834 835
    <H4><A name="4.5">4.5</A>) What is the maximum size for a row, a
    table, and a database?</H4>
836

Bruce Momjian's avatar
Bruce Momjian committed
837
    <P>These are the limits:</P>
838
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
839
    Maximum size for a database?             unlimited (500 GB databases exist)
Bruce Momjian's avatar
Bruce Momjian committed
840 841
    Maximum size for a table?                16 TB
    Maximum size for a row?                  unlimited in 7.1 and later
Bruce Momjian's avatar
Bruce Momjian committed
842
    Maximum size for a field?                1 GB in 7.1 and later
Bruce Momjian's avatar
Bruce Momjian committed
843 844 845
    Maximum number of rows in a table?       unlimited
    Maximum number of columns in a table?    250-1600 depending on column types
    Maximum number of indexes on a table?    unlimited
846
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
847 848 849
    Of course, these are not actually unlimited, but limited to
    available disk space and memory/swap space. Performance may suffer
    when these values get unusually large. 
850

Bruce Momjian's avatar
Bruce Momjian committed
851 852 853 854
    <P>The maximum table size of 16 TB does not require large file
    support from the operating system. Large tables are stored as
    multiple 1 GB files so file system size limits are not
    important.</P>
Bruce Momjian's avatar
Bruce Momjian committed
855

Bruce Momjian's avatar
Bruce Momjian committed
856 857
    <P>The maximum table size and maximum number of columns can be
    increased if the default block size is increased to 32k.</P>
Bruce Momjian's avatar
Bruce Momjian committed
858

Bruce Momjian's avatar
Bruce Momjian committed
859 860
    <H4><A name="4.6">4.6</A>) How much database disk space is required
    to store data from a typical text file?</H4>
861

Bruce Momjian's avatar
Bruce Momjian committed
862 863
    <P>A PostgreSQL database may require up to five times the disk
    space to store data from a text file.</P>
864

Bruce Momjian's avatar
Bruce Momjian committed
865
    <P>As an example, consider a file of 100,000 lines with an integer
Bruce Momjian's avatar
Bruce Momjian committed
866 867 868 869
    and text description on each line. Suppose the text string
    avergages twenty bytes in length. The flat file would be 2.8 MB.
    The size of the PostgreSQL database file containing this data can
    be estimated as 6.4 MB:</P>
870 871
<PRE>
    36 bytes: each row header (approximate)
Bruce Momjian's avatar
Bruce Momjian committed
872
    24 bytes: one int field and one text filed
873 874
   + 4 bytes: pointer on page to tuple
   ----------------------------------------
Bruce Momjian's avatar
Bruce Momjian committed
875
    64 bytes per row
876 877 878 879

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

   8192 bytes per page
Bruce Momjian's avatar
Bruce Momjian committed
880 881
   -------------------   =  128 rows per database page (rounded down)
     64 bytes per row
882

Bruce Momjian's avatar
Bruce Momjian committed
883
   100000 data rows
Bruce Momjian's avatar
Bruce Momjian committed
884 885
   --------------------  =  782 database pages (rounded up)
      128 rows per page
886

Bruce Momjian's avatar
Bruce Momjian committed
887
782 database pages * 8192 bytes per page  =  6,406,144 bytes (6.4 MB)
Bruce Momjian's avatar
Bruce Momjian committed
888
</PRE>
889

Bruce Momjian's avatar
Bruce Momjian committed
890 891
    <P>Indexes do not require as much overhead, but do contain the data
    that is being indexed, so they can be large also.</P>
Bruce Momjian's avatar
Bruce Momjian committed
892

Bruce Momjian's avatar
Bruce Momjian committed
893 894
    <H4><A name="4.7">4.7</A>) How do I find out what tables or indexes
    are defined in the database?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
895

Bruce Momjian's avatar
Bruce Momjian committed
896 897
    <P><I>psql</I> has a variety of backslash commands to show such
    information. Use \? to see them.</P>
Bruce Momjian's avatar
Bruce Momjian committed
898

Bruce Momjian's avatar
Bruce Momjian committed
899 900 901
    <P>Also try the file <I>pgsql/src/tutorial/syscat.source</I>. It
    illustrates many of the <SMALL>SELECT</SMALL>s needed to get
    information from the database system tables.</P>
Bruce Momjian's avatar
Bruce Momjian committed
902

Bruce Momjian's avatar
Bruce Momjian committed
903 904
    <H4><A name="4.8">4.8</A>) My queries are slow or don't make use of
    the indexes. Why?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
905
    Indexes are not automatically used by every query. Indexes are only
Bruce Momjian's avatar
Bruce Momjian committed
906
    used if the table is larger than a minimum size, and the query
Bruce Momjian's avatar
Bruce Momjian committed
907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925
    selects only a small percentage of the rows in the table. This is
    because the random disk access caused by an index scan is sometimes
    slower than a straight read through the table, or sequential scan. 

    <P>To determine if an index should be used, PostgreSQL must have
    statistics about the table. These statistics are collected using
    <SMALL>VACUUM ANALYZE</SMALL>, or simply <SMALL>ANALYZE</SMALL>.
    Using statistics, the optimizer knows how many rows are in the
    table, and can better determine if indexes should be used.
    Statistics are also valuable in determining optimal join order and
    join methods. Statistics collection should be performed
    periodically as the contents of the table change.</P>

    <P>Indexes are normally not used for <SMALL>ORDER BY</SMALL> or to
    perform joins. A sequential scan followed by an explicit sort is
    usually faster than an index scan of a large table.</P>
    However, <SMALL>LIMIT</SMALL> combined with <SMALL>ORDER BY</SMALL>
    often will use an index because only a small portion of the table
    is returned. 
Bruce Momjian's avatar
Bruce Momjian committed
926

Bruce Momjian's avatar
Bruce Momjian committed
927 928
    <P>When using wild-card operators such as <SMALL>LIKE</SMALL> or
    <I>~</I>, indexes can only be used if the beginning of the search
Bruce Momjian's avatar
Bruce Momjian committed
929 930 931
    is anchored to the start of the string. Therefore, to use indexes,
    <SMALL>LIKE</SMALL> patterns must not start with <I>%</I>, and
    <I>~</I>(regular expression) patterns must start with <I>^</I>.</P>
Bruce Momjian's avatar
Bruce Momjian committed
932

Bruce Momjian's avatar
Bruce Momjian committed
933 934
    <H4><A name="4.9">4.9</A>) How do I see how the query optimizer is
    evaluating my query?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
935 936 937

    <P>See the <SMALL>EXPLAIN</SMALL> manual page.</P>

Bruce Momjian's avatar
Bruce Momjian committed
938
    <H4><A name="4.10">4.10</A>) What is an R-tree index?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
939

Bruce Momjian's avatar
Bruce Momjian committed
940 941 942 943 944 945 946
    <P>An R-tree index is used for indexing spatial data. A hash index
    can't handle range searches. A B-tree index only handles range
    searches in a single dimension. R-trees can handle
    multi-dimensional data. For example, if an R-tree index can be
    built on an attribute of type <I>point</I>, the system can more
    efficiently answer queries such as "select all points within a
    bounding rectangle."</P>
Bruce Momjian's avatar
Bruce Momjian committed
947

Bruce Momjian's avatar
Bruce Momjian committed
948 949
    <P>The canonical paper that describes the original R-tree design
    is:</P>
Bruce Momjian's avatar
Bruce Momjian committed
950

Bruce Momjian's avatar
Bruce Momjian committed
951 952 953
    <P>Guttman, A. "R-trees: A Dynamic Index Structure for Spatial
    Searching." Proceedings of the 1984 ACM SIGMOD Int'l Conf on Mgmt
    of Data, 45-57.</P>
Bruce Momjian's avatar
Bruce Momjian committed
954

Bruce Momjian's avatar
Bruce Momjian committed
955 956
    <P>You can also find this paper in Stonebraker's "Readings in
    Database Systems".</P>
Bruce Momjian's avatar
Bruce Momjian committed
957

Bruce Momjian's avatar
Bruce Momjian committed
958 959 960 961
    <P>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.</P>
Bruce Momjian's avatar
Bruce Momjian committed
962

Bruce Momjian's avatar
Bruce Momjian committed
963 964
    <H4><A name="4.11">4.11</A>) What is the Genetic Query
    Optimizer?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
965

Bruce Momjian's avatar
Bruce Momjian committed
966 967 968 969
    <P>The <SMALL>GEQO</SMALL> 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.</P>
Bruce Momjian's avatar
Bruce Momjian committed
970

Bruce Momjian's avatar
Bruce Momjian committed
971 972 973
    <H4><A name="4.12">4.12</A>) How do I perform regular expression
    searches and case-insensitive regular expression searches? How do I
    use an index for case-insensitive searches?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
974

Bruce Momjian's avatar
Bruce Momjian committed
975 976 977 978
    <P>The <I>~</I> operator does regular expression matching, and
    <I>~*</I> does case-insensitive regular expression matching. The
    case-insensitive variant of <SMALL>LIKE</SMALL> is called
    <SMALL>ILIKE</SMALL> in PostgreSQL 7.1 and later.</P>
Bruce Momjian's avatar
Bruce Momjian committed
979

Bruce Momjian's avatar
Bruce Momjian committed
980 981
    <P>Case-insensitive equality comparisons are normally expressed
    as:</P>
Bruce Momjian's avatar
Bruce Momjian committed
982
<PRE>
983 984 985
    SELECT *
    FROM tab
    WHERE lower(col) = 'abc'
Bruce Momjian's avatar
Bruce Momjian committed
986 987
   
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
988 989
    This will not use an standard index. However, if you create a
    functional index, it will be used: 
Bruce Momjian's avatar
Bruce Momjian committed
990
<PRE>
991
    CREATE INDEX tabindex on tab (lower(col));
Bruce Momjian's avatar
Bruce Momjian committed
992 993
   
</PRE>
994

Bruce Momjian's avatar
Bruce Momjian committed
995 996
    <H4><A name="4.13">4.13</A>) In a query, how do I detect if a field
    is <SMALL>NULL</SMALL>?</H4>
997

Bruce Momjian's avatar
Bruce Momjian committed
998 999
    <P>You test the column with <SMALL>IS NULL</SMALL> and <SMALL>IS
    NOT NULL</SMALL>.</P>
1000

Bruce Momjian's avatar
Bruce Momjian committed
1001 1002
    <H4><A name="4.14">4.14</A>) What is the difference between the
    various character types?</H4>
1003 1004 1005 1006 1007 1008
<PRE>
Type            Internal Name   Notes
--------------------------------------------------
"char"          char            1 character
CHAR(#)         bpchar          blank padded to the specified fixed length
VARCHAR(#)      varchar         size specifies maximum length, no padding
1009
TEXT            text            no specific upper limit on length
Bruce Momjian's avatar
Bruce Momjian committed
1010
BYTEA           bytea           variable-length byte array (null-byte safe)
Bruce Momjian's avatar
Bruce Momjian committed
1011
</PRE>
1012

Bruce Momjian's avatar
Bruce Momjian committed
1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035
    <P>You will see the internal name when examining system catalogs
    and in some error messages.</P>

    <P>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 <SMALL>TOAST</SMALL>, so the space on disk
    might also be less than expected.</P>

    <P><SMALL>CHAR()</SMALL> is best when storing strings that are
    usually the same length. <SMALL>VARCHAR()</SMALL> is best when
    storing variable-length strings but it limits how long a string can
    be. <SMALL>TEXT</SMALL> is for strings of unlimited length, maximum
    1 gigabyte. <SMALL>BYTEA</SMALL> is for storing binary data,
    particularly values that include <SMALL>NULL</SMALL> bytes.</P>

    <H4><A name="4.15.1">4.15.1</A>) How do I create a
    serial/auto-incrementing field?</H4>

    <P>PostgreSQL supports a <SMALL>SERIAL</SMALL> data type. It
    auto-creates a sequence and index on the column. For example,
    this:</P>
1036
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1037 1038 1039 1040
    CREATE TABLE person ( 
        id   SERIAL, 
        name TEXT 
    );
1041
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1042
    is automatically translated into this: 
1043
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1044 1045 1046 1047 1048 1049
    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 );
1050
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064
    See the <I>create_sequence</I> manual page for more information
    about sequences. You can also use each row's <I>OID</I> field as a
    unique value. However, if you need to dump and reload the database,
    you need to use <I>pg_dump</I>'s <I>-o</I> option or <SMALL>COPY
    WITH OIDS</SMALL> option to preserve the <SMALL>OID</SMALL>s. 

    <H4><A name="4.15.2">4.15.2</A>) How do I get the value of a
    <SMALL>SERIAL</SMALL> insert?</H4>

    <P>One approach is to retrieve the next <SMALL>SERIAL</SMALL> value
    from the sequence object with the <I>nextval()</I> function
    <I>before</I> inserting and then insert it explicitly. Using the
    example table in <A href="#4.15.1">4.15.1</A>, that might look like
    this in Perl:</P>
1065
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1066 1067
    new_id = output of "SELECT nextval('person_id_seq')"
    INSERT INTO person (id, name) VALUES (new_id, 'Blaise Pascal');
1068
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079
    You would then also have the new value stored in
    <CODE>new_id</CODE> for use in other queries (e.g., as a foreign
    key to the <CODE>person</CODE> table). Note that the name of the
    automatically created <SMALL>SEQUENCE</SMALL> object will be named
    &lt;<I>table</I>&gt;_&lt;<I>serialcolumn</I>&gt;_<I>seq</I>, where
    <I>table</I> and <I>serialcolumn</I> are the names of your table
    and your <SMALL>SERIAL</SMALL> column, respectively. 

    <P>Alternatively, you could retrieve the assigned
    <SMALL>SERIAL</SMALL> value with the <I>currval</I>() function
    <I>after</I> it was inserted by default, e.g.,</P>
1080
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1081
    INSERT INTO person (name) VALUES ('Blaise Pascal');
Bruce Momjian's avatar
Bruce Momjian committed
1082
    new_id = output of "SELECT currval('person_id_seq')";
1083
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096
    Finally, you could use the <A href="#4.16"><SMALL>OID</SMALL></A>
    returned from the <SMALL>INSERT</SMALL> 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 <I>$sth-&gt;{pg_oid_status}</I> after
    <I>$sth-&gt;execute()</I>. 

    <H4><A name="4.15.3">4.15.3</A>) Don't <I>currval()</I> and
    <I>nextval()</I> lead to a race condition with other users?</H4>

    <P>No. Currval() returns the current value assigned by your
    backend, not by all users.</P>

Bruce Momjian's avatar
Bruce Momjian committed
1097 1098 1099
    <H4><A name="4.15.4">4.15.4</A>) Why aren't my sequence numbers
    reused on transaction abort? Why are there gaps in the numbering of
    my sequence/SERIAL column?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
1100 1101

    <P>To improve concurrency, sequence values are given out to running
Bruce Momjian's avatar
Bruce Momjian committed
1102
    transactions as needed and are not locked until the transaction
Bruce Momjian's avatar
Bruce Momjian committed
1103 1104
    completes. This causes gaps in numbering from aborted
    transactions.</P>
Bruce Momjian's avatar
Bruce Momjian committed
1105

Bruce Momjian's avatar
Bruce Momjian committed
1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129
    <H4><A name="4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is
    a <SMALL>TID</SMALL>?</H4>

    <P><SMALL>OID</SMALL>s are PostgreSQL's answer to unique row ids.
    Every row that is created in PostgreSQL gets a unique
    <SMALL>OID</SMALL>. All <SMALL>OID</SMALL>s generated during
    <I>initdb</I> are less than 16384 (from
    <I>backend/access/transam.h</I>). All user-created
    <SMALL>OID</SMALL>s are equal to or greater than this. By default,
    all these <SMALL>OID</SMALL>s are unique not only within a table or
    database, but unique within the entire PostgreSQL installation.</P>

    <P>PostgreSQL uses <SMALL>OID</SMALL>s in its internal system
    tables to link rows between tables. These <SMALL>OID</SMALL>s can
    be used to identify specific user rows and used in joins. It is
    recommended you use column type <SMALL>OID</SMALL> to store
    <SMALL>OID</SMALL> values. You can create an index on the
    <SMALL>OID</SMALL> field for faster access.</P>

    <P>O<SMALL>ID</SMALL>s are assigned to all new rows from a central
    area that is used by all databases. If you want to change the
    <SMALL>OID</SMALL> to something else, or if you want to make a copy
    of the table, with the original <SMALL>OID</SMALL>s, there is no
    reason you can't do it:</P>
1130 1131
<PRE>
        CREATE TABLE new_table(old_oid oid, mycol int);
Bruce Momjian's avatar
Bruce Momjian committed
1132
        SELECT old_oid, mycol INTO new FROM old;
1133 1134 1135 1136
        COPY new TO '/tmp/pgtable';
        DELETE FROM new;
        COPY new WITH OIDS FROM '/tmp/pgtable';
<!--
Bruce Momjian's avatar
Bruce Momjian committed
1137 1138
    CREATE TABLE new_table (mycol int);
    INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM old_table;
1139
-->
Bruce Momjian's avatar
Bruce Momjian committed
1140
</PRE>
1141

Bruce Momjian's avatar
Bruce Momjian committed
1142 1143 1144
    <P>O<SMALL>ID</SMALL>s 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.</P>
Bruce Momjian's avatar
Bruce Momjian committed
1145

Bruce Momjian's avatar
Bruce Momjian committed
1146 1147 1148 1149
    <P>T<SMALL>ID</SMALL>s are used to identify specific physical rows
    with block and offset values. T<SMALL>ID</SMALL>s change after rows
    are modified or reloaded. They are used by index entries to point
    to physical rows.</P>
1150

Bruce Momjian's avatar
Bruce Momjian committed
1151 1152
    <H4><A name="4.17">4.17</A>) What is the meaning of some of the
    terms used in PostgreSQL?</H4>
1153

Bruce Momjian's avatar
Bruce Momjian committed
1154 1155
    <P>Some of the source code and older documentation use terms that
    have more common usage. Here are some:</P>
1156

Bruce Momjian's avatar
Bruce Momjian committed
1157 1158
    <UL>
      <LI>table, relation, class</LI>
1159

Bruce Momjian's avatar
Bruce Momjian committed
1160
      <LI>row, record, tuple</LI>
1161

Bruce Momjian's avatar
Bruce Momjian committed
1162
      <LI>column, field, attribute</LI>
Bruce Momjian's avatar
Bruce Momjian committed
1163

Bruce Momjian's avatar
Bruce Momjian committed
1164
      <LI>retrieve, select</LI>
1165

Bruce Momjian's avatar
Bruce Momjian committed
1166
      <LI>replace, update</LI>
1167

Bruce Momjian's avatar
Bruce Momjian committed
1168 1169 1170 1171 1172 1173 1174 1175 1176
      <LI>append, insert</LI>

      <LI><SMALL>OID</SMALL>, serial value</LI>

      <LI>portal, cursor</LI>

      <LI>range variable, table name, table alias</LI>
    </UL>

Bruce Momjian's avatar
Bruce Momjian committed
1177 1178
    <P>A list of general database terms can be found at: <A href=
    "http://www.comptechnews.com/~reaster/dbdesign.html">http://www.comptechnews.com/~reaster/dbdesign.html</A></P>
1179

Bruce Momjian's avatar
Bruce Momjian committed
1180 1181
    <H4><A name="4.18">4.18</A>) Why do I get the error <I>"ERROR:
    Memory exhausted in AllocSetAlloc()"</I>?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
1182

Bruce Momjian's avatar
Bruce Momjian committed
1183 1184 1185 1186
    <P>If you are running a version older than 7.1, an upgrade may fix
    the problem. Also 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 <I>postmaster</I>:</P>
Bruce Momjian's avatar
Bruce Momjian committed
1187 1188 1189 1190
<PRE>
    ulimit -d 262144
    limit datasize 256m
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1191 1192 1193 1194 1195 1196 1197
    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 <SMALL>SQL</SMALL> client because the
    backend is returning too much data, try it before starting the
    client. 
Bruce Momjian's avatar
Bruce Momjian committed
1198

Bruce Momjian's avatar
Bruce Momjian committed
1199 1200
    <H4><A name="4.19">4.19</A>) How do I tell what PostgreSQL version
    I am running?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
1201

Bruce Momjian's avatar
Bruce Momjian committed
1202
    <P>From <I>psql</I>, type <CODE>select version();</CODE></P>
Bruce Momjian's avatar
Bruce Momjian committed
1203

Bruce Momjian's avatar
Bruce Momjian committed
1204 1205
    <H4><A name="4.20">4.20</A>) Why does my large-object operations
    get <I>"invalid large obj descriptor"</I>?</H4>
1206

Bruce Momjian's avatar
Bruce Momjian committed
1207 1208 1209
    <P>You need to put <CODE>BEGIN WORK</CODE> and <CODE>COMMIT</CODE>
    around any use of a large object handle, that is, surrounding
    <CODE>lo_open</CODE> ... <CODE>lo_close.</CODE></P>
1210

Bruce Momjian's avatar
Bruce Momjian committed
1211 1212 1213 1214 1215
    <P>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 <I>invalid large obj descriptor</I>. 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.</P>
1216

Bruce Momjian's avatar
Bruce Momjian committed
1217 1218
    <P>If you are using a client interface like <SMALL>ODBC</SMALL> you
    may need to set <CODE>auto-commit off.</CODE></P>
Bruce Momjian's avatar
Bruce Momjian committed
1219

Bruce Momjian's avatar
Bruce Momjian committed
1220 1221
    <H4><A name="4.21">4.21</A>) How do I create a column that will
    default to the current time?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
1222

Bruce Momjian's avatar
Bruce Momjian committed
1223
    <P>Use <I>CURRENT_TIMESTAMP</I>:</P>
Bruce Momjian's avatar
Bruce Momjian committed
1224
<PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1225
<CODE>CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
Bruce Momjian's avatar
Bruce Momjian committed
1226 1227
</CODE>
</PRE>
1228

Bruce Momjian's avatar
Bruce Momjian committed
1229 1230
    <H4><A name="4.22">4.22</A>) Why are my subqueries using
    <CODE><SMALL>IN</SMALL></CODE> so slow?</H4>
1231

Bruce Momjian's avatar
Bruce Momjian committed
1232 1233 1234 1235
    <P>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 <CODE>IN</CODE> with
    <CODE>EXISTS</CODE>:</P>
Bruce Momjian's avatar
Bruce Momjian committed
1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249
<PRE>
<CODE>SELECT *
    FROM tab
    WHERE col1 IN (SELECT col2 FROM TAB2)
</CODE>
</PRE>
    to: 
<PRE>
<CODE>SELECT *
    FROM tab
    WHERE EXISTS (SELECT col2 FROM TAB2 WHERE col1 = col2)
</CODE>
</PRE>
    We hope to fix this limitation in a future release. 
1250

Bruce Momjian's avatar
Bruce Momjian committed
1251
    <H4><A name="4.23">4.23</A>) How do I perform an outer join?</H4>
1252

Bruce Momjian's avatar
Bruce Momjian committed
1253 1254
    <P>PostgreSQL 7.1 and later supports outer joins using the SQL
    standard syntax. Here are two examples:</P>
Bruce Momjian's avatar
Bruce Momjian committed
1255 1256 1257 1258
<PRE>
    SELECT *
    FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1259
    or 
Bruce Momjian's avatar
Bruce Momjian committed
1260 1261 1262 1263
<PRE>
    SELECT *
    FROM t1 LEFT OUTER JOIN t2 USING (col);
</PRE>
Bruce Momjian's avatar
Bruce Momjian committed
1264

Bruce Momjian's avatar
Bruce Momjian committed
1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277
    <P>These identical queries join t1.col to t2.col, and also return
    any unjoined rows in t1 (those with no match in t2). A
    <SMALL>RIGHT</SMALL> join would add unjoined rows of t2. A
    <SMALL>FULL</SMALL> join would return the matched rows plus all
    unjoined rows from t1 and t2. The word <SMALL>OUTER</SMALL> is
    optional and is assumed in <SMALL>LEFT</SMALL>,
    <SMALL>RIGHT</SMALL>, and <SMALL>FULL</SMALL> joins. Ordinary joins
    are called <SMALL>INNER</SMALL> joins.</P>

    <P>In previous releases, outer joins can be simulated using
    <SMALL>UNION</SMALL> and <SMALL>NOT IN</SMALL>. For example, when
    joining <I>tab1</I> and <I>tab2</I>, the following query does an
    <I>outer</I> join of the two tables:<BR>
Bruce Momjian's avatar
Bruce Momjian committed
1278
    <BR>
Bruce Momjian's avatar
Bruce Momjian committed
1279
    </P>
Bruce Momjian's avatar
Bruce Momjian committed
1280 1281 1282 1283 1284 1285 1286 1287
<PRE>
    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)
Bruce Momjian's avatar
Bruce Momjian committed
1288
    ORDER BY col1
Bruce Momjian's avatar
Bruce Momjian committed
1289
</PRE>
1290

Bruce Momjian's avatar
Bruce Momjian committed
1291 1292
    <H4><A name="4.24">4.24</A>) How do I perform queries using
    multiple databases?</H4>
Bruce Momjian's avatar
Bruce Momjian committed
1293

Bruce Momjian's avatar
Bruce Momjian committed
1294 1295 1296
    <P>There is no way to query any database except the current one.
    Because PostgreSQL loads database-specific system catalogs, it is
    uncertain how a cross-database query should even behave.</P>
Bruce Momjian's avatar
Bruce Momjian committed
1297

Bruce Momjian's avatar
Bruce Momjian committed
1298 1299
    <P>Of course, a client can make simultaneous connections to
    different databases and merge the information that way.</P>
Bruce Momjian's avatar
Bruce Momjian committed
1300
    <HR>
Bruce Momjian's avatar
Bruce Momjian committed
1301

Bruce Momjian's avatar
Bruce Momjian committed
1302
    <H2 align="center">Extending PostgreSQL</H2>
1303

Bruce Momjian's avatar
Bruce Momjian committed
1304 1305
    <H4><A name="5.1">5.1</A>) I wrote a user-defined function. When I
    run it in <I>psql</I>, why does it dump core?</H4>
1306

Bruce Momjian's avatar
Bruce Momjian committed
1307 1308
    <P>The problem could be a number of things. Try testing your
    user-defined function in a stand-alone test program first.</P>
1309

Bruce Momjian's avatar
Bruce Momjian committed
1310 1311
    <H4><A name="5.2">5.2</A>) How can I contribute some nifty new
    types and functions to PostgreSQL?</H4>
1312

Bruce Momjian's avatar
Bruce Momjian committed
1313 1314 1315
    <P>Send your extensions to the <I>pgsql-hackers</I> mailing list,
    and they will eventually end up in the <I>contrib/</I>
    subdirectory.</P>
1316

Bruce Momjian's avatar
Bruce Momjian committed
1317 1318
    <H4><A name="5.3">5.3</A>) How do I write a C function to return a
    tuple?</H4>
1319

Bruce Momjian's avatar
Bruce Momjian committed
1320 1321
    <P>This requires wizardry so extreme that the authors have never
    tried it, though in principle it can be done.</P>
1322

Bruce Momjian's avatar
Bruce Momjian committed
1323 1324
    <H4><A name="5.4">5.4</A>) I have changed a source file. Why does
    the recompile not see the change?</H4>
1325

Bruce Momjian's avatar
Bruce Momjian committed
1326 1327 1328 1329 1330
    <P>The <I>Makefiles</I> do not have the proper dependencies for
    include files. You have to do a <I>make clean</I> and then another
    <I>make</I>. If you are using <SMALL>GCC</SMALL> you can use the
    <I>--enable-depend</I> option of <I>configure</I> to have the
    compiler compute the dependencies automatically.</P>
Bruce Momjian's avatar
Bruce Momjian committed
1331
  </BODY>
1332
</HTML>
Bruce Momjian's avatar
Bruce Momjian committed
1333