

- #Postgres app data directory install
- #Postgres app data directory upgrade
- #Postgres app data directory pro
- #Postgres app data directory windows
It returns a list of arguments such as "-t public.v_bpa_metric_dataflow -t public.er_v_dep_2002.
#Postgres app data directory windows
On Microsoft Windows computers, prepare the database schema manually and perform the migration using the following procedure: As a root user, start the PostgreSQL 10.x instance.įor example: systemctl start postgresql-10.

#following parameters should be tuned according to actual memory available to Database server machine Ĭopy the Client Authentication configuration file ( pg_hba.conf) from the /data folder to the /data folder.Ĭopy the following configuration parameter information from the /data/nf file and add it to the /data/nf file.
#Postgres app data directory upgrade
As the postgres user, perform the upgrade using the pg_upgrade command:įor example: /usr/pgsql-10/bin/pg_upgrade -b /usr/pgsql-9.6/bin -B /usr/pgsql-10/bin -d /var/lib/pgsql/9.6/data -D /var/lib/pgsql/10/data -k –vįor more information about the pg_upgrade command, see pg_upgrade.If the database instance is already running, as a root user, stop PostgreSQL 10.x instance by using the following command:įor example: systemctl stop postgresql-10.As a root user, initiate the PostgreSQL 10.x database using the initdb command:įor example: /usr/pgsql-10/bin/postgresql-10-setup initdb.For more information, see Installing PostgreSQL 10.x.
#Postgres app data directory install
As a root user, install and configure the PostgreSQL 10.x database.As a root user, stop the PostgreSQL 9.x instance.įor example: systemctl stop postgresql-9.6.If you select No, you can use pgsql or a DB client connected to the PostgreSQL 9.x instance to run the script.If you select Yes, the script will run and prepare the database for upgrade.The pre_upgrade_script.sql script is created, and you will be prompted whether to run this SQL script. As a postgres user, run the prepare_for_pg_upgrade.sh command to prepare the database for upgrade.Edit the customenv.sh file and set all the necessary variables.Copy the contents of this folder to a temporary directory on the TrueSight Capacity Optimization Database Server that runs the PostgreSQL 9.x database.Navigate to the following location on the computer where you have upgraded the Application Server:.On Linux computers, prepare the database schema using the pre-upgrade check utility and perform the migration using the following procedure: The PostgreSQL 10.x installation files are downloaded.The PostgreSQL 9.x instance is up and running.You have a backup of your PostgreSQL 9.x instance.All TrueSight Capacity Optimization services are stopped.TrueSight Capacity Optimization is upgraded to version 11.3.You have administrator privileges for accessing TrueSight Capacity Optimization.Microsoft Windows - Migrate the data manuallyīefore you migrate the data, ensure that the following requirements are met:.Linux - Migrate the data using the pre-upgrade check utility.You can migrate the PostgreSQL data using the following approach: Migrating is especially useful because it allows you to reuse configured information from the earlier version and saves time in getting started with the new version. In the process of upgrading, you need to migrate PostgreSQL 9.x database and configuration information to PostgreSQL 10.x. In this case, you can connect as the postgres superuser or the sde user, as the Create Enterprise Geodatabase tool granted the sde user superuser status.Ĭreate a database connection, logging in as the postgres or sde user.You can upgrade PostgreSQL version 9.x to 10.x.

To create the user, though, you must first connect to the geodatabase as the database administrator. Use the Create Database User geoprocessing tool to create a user in the PostgreSQL database cluster and a schema in your new database. Create a user to own dataĭata stored in your geodatabase should be owned by users other than the sde user. The database, sde user, sde schema, and geodatabase are created in PostgreSQL. You must also point to the keycodes file that was generated when you authorized your ArcGIS Server site.
#Postgres app data directory pro
