Skip to the main content.
Downloads Thriftly Login
Downloads Thriftly Login
Group 762

Migrate and run DataFlex applications with Oracle, MS SQL Server, PostgreSQL, MySQL &  MariaDB.

flex2Crystal

Stuck in Crystal XI?  Upgrade and use the latest versions of Crystal Reports with DataFlex applications. 

BTR2SQL

Seamlessly convert from Btrieve transactional database to PostgreSQL, Oracle, and MS SQL Server.

thriftly-1

Quickly build multi-protocol web services with the same API. Supports JSON-RPC, REST, SOAP,  Thrift, and gRPC.

 Group 671-1

 

Why Mertech?

1 min read

Configuring PostgreSQL

The Windows parameters for configuring PostgreSQL server are located in two configuration files. A few parameters in these files have to be adjusted before the server can be used in production.

Pg_hba.conf a.k.a. PostgreSQL Client Authentication Configuration File:
The purpose for this file is to identify all of the machines that are able to access PostgreSQL remotely.

This is a direct quote from the comments section of the file. “If you want to allow non-local connections, you need to add more "host" records. Also, remember TCP/IP connections are only enabled if you enable "tcpip_socket" in postgresql.conf.” 47.


The arguments required are:

Type = local or host Database = all or can specify one User = all or can specify one IP-ADDRESS = machines ip address IP-MASK = 255.255.255.0 METHOD = trust


This information must be entered for all machines and or users wanting to access PostgreSQL .

 

Postgresql.conf a.k.a. PostgreSQL Configuration File:

In this file the following must be uncommented in order for remote connections to work.

1. Connection Parameters

2. tcpip_socket = false (default)


tcpip_socket = true port = 5432 There are other settings that need to be dealt with for optimization purposes, but for connectivity purposes only these changes are required.

1. Misc

2. autocommit = true

autocommit = false

From PostgreSQL 7.3 Documentation Chapter 10 Performance Tips 10.4.1.
Disable Autocommit Turn off autocommit and just do one commit at the end. (In plain SQL, this means issuing BEGIN at the start and COMMIT at the end. Some client libraries may do this behind your back, in which case you need to make sure the library does it when you want it done.) If you allow each insertion to be committed separately, PostgreSQL is doing a lot of work for each record added.

From Start -> Program -> PostgreSQL -> Utilities Menu: Enable PostgreSQL Service From Start -> Program -> PostgreSQL -> Utilities Menu: Start PostgreSQL Server

 

 

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Introduction Many independent software vendors (ISV) and corporate users still rely on applications that use a category of database collective called...

Read More
Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

COBOL applications are the foundation of numerous essential business functions, especially within the banking, insurance, and government sectors....

Read More
Application Modernization 101: Ultimate Guide to Digital Transformation

Application Modernization 101: Ultimate Guide to Digital Transformation

Imagine breaking free from the constraints of old, monolithic systems and embracing the agility and innovation of cloud-based solutions.

Read More