10
10
alink ="#0000ff ">
11
11
< H1 > Frequently Asked Questions (FAQ) for PostgreSQL</ H1 >
12
12
13
- < P > Last updated: Sat Jan 29 22:51:43 EST 2005</ P >
13
+ < P > Last updated: Sat Jan 29 22:59:12 EST 2005</ P >
14
14
15
15
< P > Current maintainer: Bruce Momjian (< A href =
16
16
"mailto:pgman@candle.pha.pa.us "> pgman@candle.pha.pa.us</ A > )< BR >
@@ -56,24 +56,18 @@ <H2 align="center">User Client Questions</H2>
56
56
< H2 align ="center "> Administrative Questions</ H2 >
57
57
< A href ="#3.1 "> 3.1</ A > ) How do I install PostgreSQL somewhere other
58
58
than < I > /usr/local/pgsql</ I > ?< BR >
59
- < A href ="#3.2 "> 3.2</ A > ) When I start < I > postmaster</ I > , I get a
60
- < I > Bad System Call</ I > or core dumped message. Why?< BR >
61
- < A href ="#3.3 "> 3.3</ A > ) When I try to start < I > postmaster</ I > , I
62
- get < I > IpcMemoryCreate</ I > errors. Why?< BR >
63
- < A href ="#3.4 "> 3.4</ A > ) When I try to start < I > postmaster</ I > , I
64
- get < I > IpcSemaphoreCreate</ I > errors. Why?< BR >
65
- < A href ="#3.5 "> 3.5</ A > ) How do I control connections from other
59
+ < A href ="#3.2 "> 3.2</ A > ) How do I control connections from other
66
60
hosts?< BR >
67
- < A href ="#3.6 "> 3.6 </ A > ) How do I tune the database engine for
61
+ < A href ="#3.3 "> 3.3 </ A > ) How do I tune the database engine for
68
62
better performance?< BR >
69
- < A href ="#3.7 "> 3.7 </ A > ) What debugging features are available?< BR >
70
- < A href ="#3.8 "> 3.8 </ A > ) Why do I get < I > "Sorry, too many
63
+ < A href ="#3.4 "> 3.4 </ A > ) What debugging features are available?< BR >
64
+ < A href ="#3.5 "> 3.5 </ A > ) Why do I get < I > "Sorry, too many
71
65
clients"</ I > when trying to connect?< BR >
72
- < A href ="#3.9 "> 3.9 </ A > ) What is in the < I > pgsql_tmp</ I >
66
+ < A href ="#3.6 "> 3.6 </ A > ) What is in the < I > pgsql_tmp</ I >
73
67
directory?< BR >
74
- < A href ="#3.10 "> 3.10 </ A > ) Why do I need to do a dump and restore
68
+ < A href ="#3.7 "> 3.7 </ A > ) Why do I need to do a dump and restore
75
69
to upgrade PostgreSQL releases?< BR >
76
- < A href ="#3.11 "> 3.11 </ A > ) What computer hardware should I use?< BR >
70
+ < A href ="#3.8 "> 3.8 </ A > ) What computer hardware should I use?< BR >
77
71
78
72
79
73
< H2 align ="center "> Operational Questions</ H2 >
@@ -544,47 +538,7 @@ <H4><A name="3.1">3.1</A>) How do I install PostgreSQL somewhere
544
538
< P > Specify the < I > --prefix</ I > option when running
545
539
< I > configure</ I > .</ P >
546
540
547
- < H4 > < A name ="3.2 "> 3.2</ A > ) When I start < I > postmaster</ I > , I get a
548
- < I > Bad System Call</ I > or core dumped message. Why?</ H4 >
549
-
550
- < P > It could be a variety of problems, but first check to see that
551
- you have System V extensions installed in your kernel. PostgreSQL
552
- requires kernel support for shared memory and semaphores.</ P >
553
-
554
- < H4 > < A name ="3.3 "> 3.3</ A > ) When I try to start < I > postmaster</ I > , I
555
- get < I > IpcMemoryCreate</ I > errors. Why?</ H4 >
556
-
557
- < P > You either do not have shared memory configured properly in your
558
- kernel or you need to enlarge the shared memory available in the
559
- kernel. The exact amount you need depends on your architecture and
560
- how many buffers and backend processes you configure for
561
- < I > postmaster</ I > . For most systems, with default numbers of
562
- buffers and processes, you need a minimum of ~1 MB. See the < A
563
- href ="http://www.postgresql.org/docs/current/static/kernel-resources.html "> PostgreSQL
564
- Administrator's Guide/Server Run-time Environment/Managing Kernel Resources</ A >
565
- section for more detailed information about shared memory and semaphores.</ P >
566
-
567
- < H4 > < A name ="3.4 "> 3.4</ A > ) When I try to start < I > postmaster</ I > , I
568
- get < I > IpcSemaphoreCreate</ I > errors. Why?</ H4 >
569
-
570
- < P > If the error message is < I > IpcSemaphoreCreate: semget failed (No
571
- space left on device)</ I > then your kernel is not configured with
572
- enough semaphores. Postgres needs one semaphore per potential
573
- backend process. A temporary solution is to start < I > postmaster</ I >
574
- with a smaller limit on the number of backend processes. Use
575
- < I > -N</ I > with a parameter less than the default of 32. A more
576
- permanent solution is to increase your kernel's
577
- < SMALL > SEMMNS</ SMALL > and < SMALL > SEMMNI</ SMALL > parameters.</ P >
578
-
579
- < P > Inoperative semaphores can also cause crashes during heavy
580
- database access.</ P >
581
-
582
- < P > If the error message is something else, you might not have
583
- semaphore support configured in your kernel at all. See the
584
- PostgreSQL Administrator's Guide for more detailed information
585
- about shared memory and semaphores.</ P >
586
-
587
- < H4 > < A name ="3.5 "> 3.5</ A > ) How do I control connections from other
541
+ < H4 > < A name ="3.2 "> 3.2</ A > ) How do I control connections from other
588
542
hosts?</ H4 >
589
543
590
544
< P > By default, PostgreSQL only allows connections from the local
@@ -594,7 +548,7 @@ <H4><A name="3.5">3.5</A>) How do I control connections from other
594
548
host-based authentication by modifying the file
595
549
< I > $PGDATA/pg_hba.conf</ I > accordingly.</ P >
596
550
597
- < H4 > < A name ="3.6 "> 3.6 </ A > ) How do I tune the database engine for
551
+ < H4 > < A name ="3.3 "> 3.3 </ A > ) How do I tune the database engine for
598
552
better performance?</ H4 >
599
553
600
554
< P > Certainly, indexes can speed up queries. The
@@ -633,7 +587,7 @@ <H4><A name="3.6">3.6</A>) How do I tune the database engine for
633
587
data in tables to match an index. See the < SMALL > CLUSTER</ SMALL >
634
588
manual page for more details.</ P >
635
589
636
- < H4 > < A name ="3.7 "> 3.7 </ A > ) What debugging features are
590
+ < H4 > < A name ="3.4 "> 3.4 </ A > ) What debugging features are
637
591
available?</ H4 >
638
592
639
593
< P > PostgreSQL has several features that report status information
@@ -691,7 +645,7 @@ <H4><A name="3.7">3.7</A>) What debugging features are
691
645
file will be put in the client's current directory. Linux requires
692
646
a compile with < I > -DLINUX_PROFILE</ I > for proper profiling.</ P >
693
647
694
- < H4 > < A name ="3.8 "> 3.8 </ A > ) Why do I get < I > "Sorry, too many
648
+ < H4 > < A name ="3.5 "> 3.5 </ A > ) Why do I get < I > "Sorry, too many
695
649
clients"</ I > when trying to connect?</ H4 >
696
650
697
651
< P > You need to increase < I > postmaster</ I > 's limit on how many
@@ -716,7 +670,7 @@ <H4><A name="3.8">3.8</A>) Why do I get <I>"Sorry, too many
716
670
the number of allowed backend processes is so your system won't run
717
671
out of resources.</ P >
718
672
719
- < H4 > < A name ="3.9 "> 3.9 </ A > ) What is in the < I > pgsql_tmp</ I > directory?</ H4 >
673
+ < H4 > < A name ="3.6 "> 3.6 </ A > ) What is in the < I > pgsql_tmp</ I > directory?</ H4 >
720
674
721
675
< P > This directory contains temporary files generated by the query
722
676
executor. For example, if a sort needs to be done to satisfy an
@@ -728,7 +682,7 @@ <H4><A name="3.9">3.9</A>) What is in the <I>pgsql_tmp</I> directory?</H4>
728
682
remain if a backend crashes during a sort. A stop and restart of the
729
683
< I > postmaster</ I > will remove files from those directories.</ P >
730
684
731
- < H4 > < A name ="3.10 "> 3.10 </ A > ) Why do I need to do a dump and restore
685
+ < H4 > < A name ="3.7 "> 3.7 </ A > ) Why do I need to do a dump and restore
732
686
to upgrade between major PostgreSQL releases?</ H4 >
733
687
734
688
< P > The PostgreSQL team makes only small changes between minor releases,
@@ -744,7 +698,7 @@ <H4><A name="3.10">3.10</A>) Why do I need to do a dump and restore
744
698
The release notes mention whether < I > pg_upgrade</ I > is available for the
745
699
release.</ P >
746
700
747
- < H4 > < A name ="3.11 "> 3.11 </ A > ) What computer hardware should I use?</ H4 >
701
+ < H4 > < A name ="3.8 "> 3.8 </ A > ) What computer hardware should I use?</ H4 >
748
702
749
703
< P > Because PC hardware is mostly compatible, people tend to believe that
750
704
all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
0 commit comments