Welcome to this release V8.4.1 Postgres SQL Server for OS / 2!

I thank in advance all the people who believed in this project,
and even those who did not believe it!
I hope that you will be more and more 'to use this DBMS, which also
also won some awards.

I wrote this to try to help solve some small
problems and understand certain things, without consulting dozens of pages of
documentation.

Ok, we begin!

My last port back to version 7.3 of Postgres. During this period
I got married, I had children, they have grown and now I have more '
time for Postgres and other port.
The porting difference between version 7.3 and 8.4 mainly
the use of the compiler (GCC 3.3.5).
All libraries being compiled with GCC 3.3.5 can be linked with
the new software.

Since there is no link in the native filesystem of OS/2, I have broken the
engine into three parts: postgres.dll, postgres.exe, postmaster.exe
The two. EXE although the same size, actually performing the
different calls within the DLL, then don't overwrite!

For each new user who logs in, the engine makes a fork itself and
postgres.dll charging ram, which in this version is about 4.8 Mb
The data in the DBMS are kept in RAM and shared during the fork
thus employment in RAM for each user should be minimal!

Others. EXE are utilities to administer the database and are all VIO.
At about the .EXE utilities, I remind you that you can use to
administer the database locally (on your machine, OS/2)
or remotely on other systems (UNIX, NT, etc.).
If you read the documentation, you know how!.

By the way, there is one main script (PGCMD.CMD) that you need to run
Utilities Administration Postgres and also its launch and closure.
This serves to believe Postgres and utilities that are working
within a UNIX (which is very important for Postgres).
but also serves to create a non-intrusive environment for OS/2.
Indeed Postgres does not invade OS/2 and does not disturb the execution of other
programs or their configuration: TCP/IP, MPTN, etc..
The only change is the addition of two environment variable in CONFIG.SYS
PGDATA (database directory) and PGSQL (directory Postgres)

SET PGSQL=c:\apps\pgsql841
SET PGDATA=c:\pgsqldata
SET ENDLIBPATH=%ENDLIBPATH%;c:\apps\pgsql841\lib;

Just extract the archive, then perform these steps:

-- Add at variable ENDLIBPATH the path of Postgres "LIB" directory
   [C:\apps\pgsql841]set ENDLIBPATH=%ENDLIBPATH%;c:\apps\pgsql841\lib;

-- Set the variable PGSQL with the path of Postgres directory
   for example: [C:\apps\pgsql841set pgsql=c:\apps\pgsql841

-- Create a directory where the database resides
   For example: md c:\pgsqldata

-- Set the variable PGDATA with the path of directory previously created
   for example: [C:\apps\pgsql841]set PGDATA=c:\pgsqldata

-- Run the init Postgres with this command and we can see the contents below:
   [C:\apps\pgsql841] pgcmd.cmd initdb


For example:

[C:\apps\pgsql841]pgcmd initdb

[C:\apps\pgsql841\bin]initdb
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale it_IT_EURO.ISO8859-1.
The default database encoding has accordingly been set to LATIN1.
The default text search configuration will be set to "italian".

fixing permissions on existing directory d:/pgsqldata ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 32MB
creating configuration files ... ok
creating template1 database in d:/pgsqldata/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.

Success. You can now start the database server using:

    "postgres" -D "c:/pgsqldata"
    or
    "pg_ctl" -D "c:/pgsqldata" -l logfile start


[C:\apps\pgsql841]


If everything be well, we can start Postgres with this command:
[C:\apps\pgsql841] pgcmd.cmd pg_ctl start

Or stop it with this command:
[C:\apps\pgsql841] pgcmd.cmd pg_ctl stop

As you can see, all commands are executed through Postgres
PGCMD.CMD script.


Ok, for the time being everything!
If you have problems do not hesitate to contact me, I'll try to answer all!

PS: I do not speak English very well, so if you do not speak Italian be
preferred that you contact me via email, or please contact us
after 17:00 (TZ GMT +1)

Ciao.

Vincenzo Venuto

Address: Italy
Tel:     +39-335-6059667
eMail:   postgres@ecomstation.it

S.E.T.I. Project supporter
Postgres SQL Server for OS/2 developer
Unix/Linux to OS/2 developer
Minnesota Map Server for OS/2 developer
