Configure the connection to the pgpro_metastore catalog server:

SELECT metastore.define_catalog_connection('host', 'port', 'DB_name', 'username', 'password')

Where:

If one of these parameters is missing, for example, when connecting to the pgpro_metastore catalog server without a user password, pass an empty string instead of a value:

SELECT metastore.define_catalog_connection('host','port','DB_name','','');

For the changes to take effect, reconnect to the pgpro_metastore server (not to the pgpro_metastore catalog server).

If the connection to the pgpro_metastore catalog server fails, you are automatically reconnected using the last connection parameters:

postgres=# SELECT metastore.remove_storage('mt_storage');
INFO:  Connection failed! Trying to reconnect.
INFO:  Reconnecting...1
INFO:  Reconnect successful!
        remove_storage
-----------------------------------
Storage was removed successfully.
(1 row)

Create the pgpro_metastore catalog:

SELECT metastore.init(force_init bool DEFAULT false)

If the pgpro_metastore catalog is already created on the server, you receive a warning:

postgres=# SELECT metastore.init();
INFO:  Metastore catalog already initialized on remote server
INFO:  Run metastore.init(true) to force rewrite catalog on remote server
init
------

(1 row)

In this case, you can recreate the pgpro_metastore catalog by executing the same query with force_init set to true:

  postgres=# SELECT metastore.init(true);
  init
  ------

  (1 row)