|
belladati_dbuser
). Remember this database user name, as it will be used to configure BellaDati's connection to this database in subsequent steps. Do not forget to configure the pg_hba.conf
file, which controls the database access.
$ createuser -SDRP belladati_dbuser |
belladati_db
) with Unicode collation.
CREATE DATABASE belladati_db WITH ENCODING 'UNICODE'; |
$ createdb -E UNICODE -O belladati_dbuser belladati_db |
CREATE LANGUAGE plpgsql |
$ createlang -U belladati_dbuser plpgsql belladati_db |
When using the default PostgreSQL configuration file |
Remember the database name; it will be used to configure BellaDati's connection to the database in subsequent steps. |
We strong recommend performing the following PostgreSQL configuration changes in $POSTGRES_HOME/data/postgresql.conf
. This example specifies parameters when you run the BellaDati application and database on a single server with 4GB memory. 2GB are allocated for the BellaDati application server running on Java (using the -Xmx parameter). The rest should be available for the operating system and database server.
Name |
Value |
Note |
---|---|---|
max_connections |
50 |
|
shared_buffers |
512MB |
min 1/4 RAM |
temp_buffers |
2MB |
per session |
work_mem |
10MB |
per client connection |
maintenance_work_mem |
64MB |
|
max_stack_depth |
2MB |
|
wal_buffers |
512kB |
|
effective_cache_size |
512MB |
|
log_statement |
none |
|
We recommend set the |
You can backup the BellaDati database using the PostgreSQL dump command:
pg_dump -U user -F c -v -f "path_to_dump/dump.backup" belladati_db |
To restore a backup, use the pg_restore
command:
pg_restore -v -c -O -d belladati_db -U user path_to_dump/dump.backup |
Continue configuring BellaDati WAR for your application server as described on: