@@ -324,7 +324,7 @@ <H4><A NAME="1.6">1.6</A>) Where can I get support for PostgreSQL?</H4><P>
324
324
via the PostgreSQL WWW home page at:
325
325
326
326
< BLOCKQUOTE >
327
- < A HREF ="http://postgreSQL.org "> http://postgreSQL.org</ A >
327
+ < A HREF ="http://www. postgreSQL.org "> http://www. postgreSQL.org</ A >
328
328
</ BLOCKQUOTE > < P >
329
329
330
330
There is also an IRC channel on EFNet, channel #PostgreSQL.
@@ -573,6 +573,7 @@ <H2><CENTER>Administrative Questions</CENTER></H2><P>
573
573
574
574
< H4 > < A NAME ="3.1 "> 3.1</ A > ) Why does initdb fail?</ H4 > < P >
575
575
576
+ Try these:
576
577
< UL >
577
578
< LI > check that you don't have any of the previous version's binaries in
578
579
your path
@@ -593,7 +594,7 @@ <H4><A NAME="3.3">3.3</A>) When I start the postmaster, I get a <I>Bad
593
594
System Call</ I > or core dumped message. Why?</ H4 > < P >
594
595
595
596
It could be a variety of problems, but first check to see that you
596
- have system V extensions installed in your kernel. PostgreSQL requires
597
+ have System V extensions installed in your kernel. PostgreSQL requires
597
598
kernel support for shared memory and semaphores.< P >
598
599
599
600
@@ -750,7 +751,7 @@ <H4><A NAME="3.12">3.12</A>) I get 'Sorry, too many clients' when trying
750
751
You need to increase the postmaster's limit on how many concurrent backend
751
752
processes it can start.< P >
752
753
753
- In Postgres 6.5 and up, the default limit is 32 processes. You can
754
+ In PostgreSQL 6.5 and up, the default limit is 32 processes. You can
754
755
increase it by restarting the postmaster with a suitable < I > -N</ I >
755
756
value. With the default configuration you can set < I > -N</ I > as large as
756
757
1024; if you need more, increase < SMALL > MAXBACKENDS</ SMALL > in
@@ -768,11 +769,11 @@ <H4><A NAME="3.12">3.12</A>) I get 'Sorry, too many clients' when trying
768
769
< SMALL > SEMMNS</ SMALL > and < SMALL > SEMMNI,</ SMALL > the maximum number of
769
770
processes, < SMALL > NPROC,</ SMALL > the maximum number of processes per
770
771
user, < SMALL > MAXUPRC,</ SMALL > and the maximum number of open files,
771
- < SMALL > NFILE</ SMALL > and < SMALL > NINODE.</ SMALL > The reason that Postgres
772
+ < SMALL > NFILE</ SMALL > and < SMALL > NINODE.</ SMALL > The reason that PostgreSQL
772
773
has a limit on the number of allowed backend processes is so that you
773
774
can ensure that your system won't run out of resources.< P >
774
775
775
- In Postgres versions prior to 6.5, the maximum number of backends was
776
+ In PostgreSQL versions prior to 6.5, the maximum number of backends was
776
777
64, and changing it required a rebuild after altering the MaxBackendId
777
778
constant in < I > include/storage/sinvaladt.h.</ I > < P >
778
779
@@ -872,7 +873,7 @@ <H4><A NAME="4.6">4.6</A>) What is the maximum size for a
872
873
< H4 > < A NAME ="4.7 "> 4.7</ A > )How much database disk space is required to
873
874
store data from a typical flat file?< BR > </ H4 > < P >
874
875
875
- A Postgres database can require about six and a half times the disk space
876
+ A PostgreSQL database can require about six and a half times the disk space
876
877
required to store the data in a flat file.< P >
877
878
878
879
Consider a file of 300,000 lines with two integers on each line. The
@@ -948,7 +949,7 @@ <H4><A NAME="4.10">4.10</A>) How do I see how the query optimizer is
948
949
949
950
< H4 > < A NAME ="4.11 "> 4.11</ A > ) What is an R-tree index?</ H4 > < P >
950
951
951
- An r -tree index is used for indexing spatial data. A hash index can't
952
+ An R -tree index is used for indexing spatial data. A hash index can't
952
953
handle range searches. A B-tree index only handles range searches in a
953
954
single dimension. R-tree's can handle multi-dimensional data. For
954
955
example, if an R-tree index can be built on an attribute of type < I > point,</ I >
@@ -1027,14 +1028,14 @@ <H4><A NAME="4.16.1">4.16.1</A>) How do I create a
1027
1028
serial/auto-incrementing field?</ H4 > < P >
1028
1029
1029
1030
PostgreSQL supports < SMALL > SERIAL</ SMALL > data type. It auto-creates a
1030
- sequence and index on the column. For example, this...
1031
+ sequence and index on the column. For example, this:
1031
1032
< PRE >
1032
1033
CREATE TABLE person (
1033
1034
id SERIAL,
1034
1035
name TEXT
1035
1036
);
1036
1037
</ PRE >
1037
- ... is automatically translated into this...
1038
+ is automatically translated into this:
1038
1039
< PRE >
1039
1040
CREATE SEQUENCE person_id_seq;
1040
1041
CREATE TABLE person (
@@ -1049,7 +1050,6 @@ <H4><A NAME="4.16.1">4.16.1</A>) How do I create a
1049
1050
you need to dump and reload the database, you need to use < I > pg_dump's -o</ I >
1050
1051
option or < SMALL > COPY WITH OIDS</ SMALL > option to preserve the oids.< P >
1051
1052
1052
- For more details, see Bruce Momjian's chapter on
1053
1053
< A HREF ="http://www.postgresql.org/docs/aw_pgsql_book "> Numbering Rows.</ A >
1054
1054
1055
1055
< H4 > < A NAME ="4.16.2 "> 4.16.2</ A > ) How do I get the back the generated SERIAL value after an insert?</ H4 > < P >
0 commit comments