Skip to the main content.
Downloads Try Thriftly
Downloads Try Thriftly
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

Convert from Btrieve / P.SQL / Actian transactional engines to Oracle, MS SQL Server, and PostgreSQL

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

 

 

Legacy Application Modernization: Key Steps, Benefits & Best Practices

Legacy Application Modernization: Key Steps, Benefits & Best Practices

This blog post was co-authored with Riaz Merchant, President and CEO at Mertech. In the fast-paced software world, 'legacy' often signals a warning.

Read More
Hybrid Cloud Migration: Plan, Process and Advantages

Hybrid Cloud Migration: Plan, Process and Advantages

This post was co-authored with Riaz Merchant, President/CEO at Mertech Data Systems, Inc.

Read More
Financial Benefits of Cloud Migration & Hybrid Cloud Applications

Financial Benefits of Cloud Migration & Hybrid Cloud Applications

Shifting from your traditional legacy systems to the Cloud can be a game changer, as the benefits of cloud migration are numerous. Cloud computing...

Read More