1
1
=======================================================
2
- Frequently Asked Questions (FAQ) for PostgreSQL V6.5
2
+ Frequently Asked Questions (FAQ) for PostgreSQL V7.0
3
3
SCO UnixWare and OpenServer Specific
4
4
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
5
5
=======================================================
6
- last updated: Tue May 25 12:00:00 PDT 1999
6
+ last updated: Mon Apr 24 04:31:44 EDT 2000
7
7
8
- current maintainer: Andrew Merrill (andrew@compclass.com )
8
+ current maintainer: Billy G. Allie (Bill.Allie@mug.org )
9
9
original author: Andrew Merrill (andrew@compclass.com)
10
10
11
11
12
- PostgreSQL 6.5 can be built on SCO UnixWare 7 and SCO OpenServer 5.
12
+ PostgreSQL 7.0 can be built on SCO UnixWare 7 and SCO OpenServer 5.
13
13
On OpenServer, you can use either the OpenServer Development Kit or
14
14
the Universal Development Kit.
15
15
@@ -21,6 +21,7 @@ Topics:
21
21
*) C++ and libpq++
22
22
*) Readline
23
23
*) Using the UDK on OpenServer
24
+ *) Compiling PostgreSQL using the UDK
24
25
*) Shared Memory and SHMMAX
25
26
*) Java and JDBC
26
27
*) Reading the PostgreSQL man pages on UnixWare
@@ -114,6 +115,38 @@ Putting these together with the no-C++ and readline options from above:
114
115
115
116
./configure --with-template=unixware --with-libs="/udk/usr/lib /usr/local/lib" --with-includes="/udk/usr/include /usr/local/include" --without-CXX
116
117
118
+ ***************************************************************************
119
+ *) Compiling PostgreSQL 7.0 with the UDK
120
+
121
+ The program, backend/utils/adt/int8.c, tickles a compiler bug with in the
122
+ following version of the C compiler:
123
+
124
+ Optimizing C Compilation System (CCS) 3.2 08/18/98 (u701)
125
+
126
+ If you encounter an error compiling backend/utils/adt/int8.c, please apply
127
+ the following patch:
128
+
129
+ ------------------------------8< CUT HERE >8------------------------------
130
+ *** ./src/backend/utils/adt/int8.c.orig Mon Apr 3 13:24:12 2000
131
+ --- ./src/backend/utils/adt/int8.c Mon Apr 3 13:28:47 2000
132
+ ***************
133
+ *** 410,416 ****
134
+ if (*arg1 < 1)
135
+ *result = 0;
136
+ else
137
+ ! for (i = *arg1, *result = 1; i > 0; --i)
138
+ *result *= i;
139
+
140
+ return result;
141
+ --- 410,416 ----
142
+ if (*arg1 < 1)
143
+ *result = 0;
144
+ else
145
+ ! for (i = *arg1, *result = 1; 0 < i; --i)
146
+ *result *= i;
147
+
148
+ return result;
149
+ ------------------------------8< CUT HERE >8------------------------------
117
150
118
151
***************************************************************************
119
152
*) Shared Memory and SHMMAX
@@ -221,26 +254,44 @@ By default, the PostgreSQL man pages are installed into /usr/local/pgsql/man.
221
254
By default, UnixWare does not look there for man pages, so you will not
222
255
be able to read them.
223
256
224
- You need to make two changes to access the PostgreSQL man pages from UnixWare.
257
+ You need to make the following changes to access the PostgreSQL man pages
258
+ from UnixWare.
259
+
260
+ 1) You need to modify the MANPATH variable in /etc/default/man. I use:
225
261
226
- 1) You need to modify the MANPATH environment variable. I use:
262
+ MANPATH=/usr/lib/scohelp/%L/man:/usr/dt/man:/usr/man:/usr/share/man:scohelp:/usr/local/man:/usr/local/pgsql/man
227
263
228
- MANPATH=/usr/local/pgsql/man:/usr/dt/man:/usr/man:/usr/share/man:scohelp
229
- export MANPATH
264
+ 2) Add a line that says '1sql' to /etc/default/manSection.
230
265
231
- 2) The man pages for SQL commands are, by default, placed in section l
232
- (normally used for "l"ocal pages). UnixWare does not support the l section.
266
+ 3) The man pages for SQL commands are, by default, placed in section 'l'
267
+ (normally used for "l"ocal pages). UnixWare does not support the 'l'
268
+ section.
233
269
234
- The solution I use is to move all these pages from section l to an unused
235
- section, such as section 6. To accomplish that:
270
+ The solution I use is to move all these pages from section 'l' to a section
271
+ named '1sql'. To following KSH script will perform the move and change the
272
+ section names in the man page:
236
273
274
+ ------------------------------8< CUT HERE >8------------------------------
275
+ #!/bin/ksh
237
276
cd /usr/local/pgsql/man
238
- mv manl man6
239
- cd man6
240
- for file in *.l
277
+ mv man1 man.1
278
+ mkdir ../man.1sql
279
+
280
+ cd /usr/local/pgsql/man/manl
281
+ for i in *.l
241
282
do
242
- mv $file `basename $file .l`.6
283
+ sed -e '/^\.TH/s/"l"/"1sql"/' $i >../man.1sql/${i%.l}.1sql
243
284
done
285
+ cd /usr/local/pgsql/man
286
+ rm -rf manl
287
+ ------------------------------8< CUT HERE >8------------------------------
288
+
289
+ After running this script, you can view the man pages using the 'man'
290
+ command. They will not be usable from the scohelp system.
291
+
292
+ I am working on integrating the man pages into the scohelp system. When I
293
+ generate a PostgreSQL package for UnixWare 7.x, the man pages will be
294
+ integrated into the scohelp system.
244
295
245
296
I have not tried using the PostgreSQL man pages on OpenServer. Volunteers??
246
297
0 commit comments