PostgreSQL
| With the PostgreSQL app in , you can run your custom logic directly on your database server through functions. loads the interface of input and output parameters dynamically so each parameter can be mapped individually. |
---|
To use the PostgreSQL app in , you must make sure sure the account you're using to connect to your database has read access to information_schema.routines and information_schema.parameters tables.
will make connections to your database from specifc IP addresses. Our servers are set up with valid PTR records so you can restrict access by allowing %.make.com.
To create the connection:
Log in to your account, add a PostgreSQL module to your , and click Create a connection.
Optional: In the Connection name field, enter a name for the connection.
Enter information for the following fields:
Field | Description |
---|---|
Host | Enter the PostgreSQL database host. |
Port | Enter the port. This must be a number between 1 and 65535. |
Database | Enter the PostgreSQL database. |
User name | Enter your user name. |
Password | Enter your password. |
Client Encoding | Enter the charset for the connection. |
Encrypt | Select Yes or No. |
Keep-Alive | Select Yes, No, or Empty. This enables TCP keep-alive to maintain idele connections. |
Keep-Alive Delay | Enter the initial delay in milliseconds for the first TCP keep-alive message. |
Click Save.
If prompted, authenticate your account and confirm access.
You've successfully created the connection and can now use the PostgreSQL app in your . If you want to make changes to your connection in the future, follow the steps here.
You can use the following modules to build your .
- Delete row(s) from a table
- Execute a function
- Execute a query (advanced)
- Insert row into a table
- Update row(s) in a table
- Select row(s) from a table
The ER_Lock_Wait_Timeout: Lock wait timeout exceeded; try restarting transaction error occurs when you modify the same data using multiple modules. It is caused by SQL transactions.
When any SQL module is executed, it starts the transaction and the transaction is finished after the is fully executed. If another module tries to access the same data used in another unfinished transaction, then it has to wait until the previous transaction is finished – but it never happens because the first transaction will be finished after the is finished.
To solve this, turn on Auto-commit. It finishes (commits) every transaction immediately after the module execution is done.
Open the settings.
Enable the Auto commit checkbox.
Click OK to confirm the settings.

Here is a sample SQL statement that creates a function that inserts the values passed in the three parameters into a table: