Installation steps

Gluesync SQL to NoSQL for PostgreSQL

Prerequisites

In order to have Gluesync working on your PostgreSQL instance you will need to have:

valid user credentials with permissions of reading, create triggers and writing to the target tables and respective database

To create a valid user for Gluesync on your Oracle database to run GDC you can run / adapt the following query:

CREATE USER gluesync SUPERUSER;
ALTER USER gluesync WITH PASSWORD 'youdecide';

Basic configuration example

This module can be customized by using a configuration file, in JSON format. The file name to use must be specified as parameter when launching the app, with the -f or --file tokens. The file should be composed by union of common configuration file (see here Installation steps) and source/destination specific configuration:

{
  ...
  "postgresql": {
    "certificatesPath": "/path/to/certs/dir/cert.pem"
  },

  "sourceChangeRetention": 5
}

PostgreSQL specific configurations are listed under the postgresql property:

certificatesPath (optional): the path to the certificates that need to be used when connecting to a PostgreSQL instance using a secure connection. If omitted, no certificates are used;

You can also specify few other options that applies to this configuration, like: * sourceChangeRetention (optional): defaults to 5. Number of retention days preserved into the Gluesync GDC action_logs table inside your Postgres database;

Looking for data modelling features or other options?

For more detailed configurations options, including the ability to perform data modelling, please have a look at the dedicated Data modelling section when sourcing from a RDBMS.