This section introduces PostgreSQL installation procedure. Please refer to PostgreSQL for precise explanation.
The examples provided in this document assume the following:
Substitute the above constants for the examples provided hereafter according to your real environment.
Consult Chapter 20 if PostgreSQL can not run.
on-premises PostERP runs not only on Windows operating system but also on WINE version 2.0 running on Linux. To run server program, simply place files server.exe and libpq.dll under the same sub-directory in Linux and type the following command wine server.exe & in X window to run application server:
Likewise, to run client program, type command wine tc.exe & instead.
If you are a Windows user and drop PostgreSQL cluster space by deleting C:\Program Files\PostgreSQL\11\data and then recreating the cluster space using command C:\Program Files\PostgreSQL\11\bin\initdb.exe, and can no longer start PostgreSQL service since then, and Windows event log says could not create lock file "postmaster.pid": Permission denied, this suggestion excerpted from http://forumserver.twoplustwo.com/114/pokertracker/cant-connect-db-422617/ might help:
Issue the following command as root login to install PostgreSQL:
apt-get install postgresql-11 apt-get install postgresql-client-11
Type the following command under psql prompt to make sure that UTF8 is the default Encoding of database cluster:
Verify that Database Cluster Space is intialized to use UTF8 as default characterset encoding:
Previous versions of PostgreSQL installation packages for Windows and Debian wheezy probably create database cluster using SQL_ASCII as default characterset encoding rather than UTF8
If this database cluster does not use UTF8 as the default character set encoding, you will encounter large number of errors when you try to restore PostERP database Section 13.2 from backup file! Debian users can wipe out the new SQL_ASCII database cluster all together and manually recreate it forcing it to use UTF8:
pg_dropcluster --stop 11 main pg_createcluster -u postgres -e UTF8 11 main
If you are a Windows user and drop PostgreSQL cluster space by deleting C:\Program Files\PostgreSQL\11\data and then recreating the cluster space using command C:\Program Files\PostgreSQL\11\bin\initdb.exe, and can no longer start PostgreSQL service since then, and Windows event log says could not create lock file "postmaster.pid": Permission denied, resource Chapter 20 might help.
Enable connecting to PostgreSQL server with role postgres
PostgreSQL role postgres will be used to perform the following tasks:
You will restore our database backup file to your PostgreSQL database.
You will do various management jobs like making backups for your PostgreSQL database.
PostERP server will connect via TCP/IP and log in to PostgreSQL in order to manipulate database without restriction.
PostERP's architecture is 3-tier computing: Database server communicates only with PostERP server; PostERP server communicates only with PostERP clients. Hence IT personnel must grant only PostERP server and no one else the acceess privilige to PostgreSQL server.
For Windows version of PostgreSQL, configure this file "C:\Program Files\PostgreSQL\11\data\pg_hba.conf" as below.
For Debian or Debian versions of PostgreSQL, configure this file /etc/postgresql/11/main/pg_hba.conf as below.
Ensure TCP connection is enabled so that role postgres can connect to PostgreSQL. Three examples of configuration:
host all postgres 127.0.0.1/32 md5 host all postgres 192.168.0.2/32 password host all postgres 192.168.0.2/32 trust
Tell PostgreSQL server to respond to the requests sent to all its interfaces by setting postgresql.conf:
listen_addresses = "*"
PostERP server establishes a certain number of connections to PostgreSQL server for every language. If the maximal number of connection is set too low, PostERP server will not start. Refer to Section 17.2 for calculation of connection number. The default limit 20 specified in postgresql.conf is sufficient in most cases:
max_connections = 20 # (change requires restart)
Restart PostgreSQL server:
Stop postgres service, then restart it.
Open a DOS window and issue this command:
"C:\Program Files\PostgreSQL\11\bin\psql.exe" -h 192.168.0.1 -U postgres -l
Unix users will send this command:
psql -h 192.168.0.1 -U postgres -l
Enter the password for account postgres. If no error message pops out, then most likely PostgreSQL server is ready to provid services.