Stelo Technical Documents

PostgreSQL Tips

Last Update: 23 May 2023
Product: SQDR & SQDR Plus
Version: 4.50 and later
Article ID: SQV00PL053


This technical document contains tips and troubleshooting hints when using SQDR for replication to and from PostgreSQL.

See also


Memory exhaustion on Postgres destination

While performing baselines of large tables to an EDB Advanced Postgres destination, the RAM usage of the postgres process on the destination system continued increasing until it reached a limit and the process aborted.

It was discovered that auditing was enabled. Disable auditing by setting edb_audit = 'none' in the postgresql.conf file. This option is available only in EDB Postgres versions.

SSL from Tier 2 (Stelo Capture aka SQDR Plus)

To connect via TLS/SSL without validating the certificate, leave the Use SSL checkbox in the Add Agent wizard as unchecked. The JDBC driver defaults to a non-validating SSL connection.

To enable certificate validation either

  • Create an agent without certificate validation. Then edit the configuration, adding the following to the sourceDbUrl property. Saving the configuration will restart the agent.
    ?ssl=true;sslrootcert=C:\ProgramData\StarQuest\sqdrplus\keystore (Windows)
    ?ssl=true;sslrootcert=C:/var/sqdrplus/keystore (Linux)
  • Or create a root certificate file in the default location expected by the JDBC driver (see below) and select the Use SSL checkbox in the Add Agent Wizard.

The default location of the root certifcate store is %APPDATA%\postgresql\root.crt (Windows) or ~/.postgresql/root.crt (Linux). Examples:

  • C:\Windows\system32\config\systemprofile\AppData\Roaming\postgresql\root.crt
  • /home/sqdr/.postgresql/root.crt


If you encounter this error when connecting to the PostgreSQL server during creation of an agent, refer to the jetty wrapper log for details.

Request Failed 500 Server Error: the call failed on the server; see server for details

SSL from Tier 3 (Stelo Apply aka SQDR)

Refer to the documentation for the ODBC driver for details.

Here are some connection string examples extracted from the Using Connection Strings chapter of the SQDR Help file.

You can also use ODBC Configuration to configure ODBC data sources.

PostgreSQL (SQDR Postgres bundled ODBC driver)

This example shows connecting via TLS/SSL to Azure Database for Postgres without validating the certificate:;Database=postgres;PortNumber=5432;EncryptionMethod=1;ValidateServerCertificate=0,

This example shows connecting via TLS/SSL to AWS RDS for Postgres, validating the certificate downloaded from AWS, and requiring TLS 1.2:;Database=postgres;PortNumber=5432;EM=1;VSC=1;TrustStore=C:\aws\global-bundle.pem;CPV=TLSV1.2


PostgreSQL (psqlODBC driver);Database=postgres;Port=5432;MaxVarcharSize=32767;MaxLongVarcharSize=214748364;SSLMode=require;Database=postgres;Port=5432;MaxVarcharSize=32767;MaxLongVarcharSize=214748364;SSLMode=verify-ca;pqopt={sslrootcert=C:\\aws\\global-bundle.pem}



The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.