node-red-contrib-postgresql is a Node-RED node to query a PostgreSQL 🐘 database.
It supports splitting the resultset and backpressure (flow control), to allow working with large datasets.
It supports parameterized queries and multiple queries.
The response (rows) is provided in msg.payload as an array.
An exception is if the Split results option is enabled and the Number of rows per message is set to 1,
then msg.payload is not an array but the single-row response.
Additional information is provided as msg.pgsql.rowCount and msg.pgsql.command.
See the underlying documentation for details.
In the case of multiple queries, then msg.pgsql is an array.
This node uses the Mustache template system to generate queries based on the message:
-- INTEGER id column
SELECT * FROM table WHERE id = {{{ msg.id }}};
-- TEXT id column
SELECT * FROM table WHERE id = '{{{ msg.id }}}';As an alternative to using the query template above, this node also accepts an SQL query via the msg.query parameter.
Parameters for parameterized queries can be passed as a parameter array msg.params:
// In a function, provide parameters for the parameterized query
msg.params = [ msg.id ];-- In this node, use a parameterized query
SELECT * FROM table WHERE id = $1;As an alternative to numeric parameters,
named parameters for parameterized queries can be passed as a parameter object msg.queryParameters:
// In a function, provide parameters for the named parameterized query
msg.queryParameters.id = msg.id;-- In this node, use a named parameterized query
SELECT * FROM table WHERE id = $id;Note: named parameters are not natively supported by PostgreSQL, and this library just emulates them, so this is less robust than numeric parameters.
If the information about which database server to connect and how needs to be dynamic, it is possible to pass a custom client configuration in the message:
msg.pgConfig = {
user?: string, // default process.env.PGUSER || process.env.USER
password?: string, //or function, default process.env.PGPASSWORD
host?: string, // default process.env.PGHOST
database?: string, // default process.env.PGDATABASE || process.env.USER
port?: number, // default process.env.PGPORT
connectionString?: string, // e.g. postgres://user:password@host:5432/database
ssl?: any, // passed directly to node.TLSSocket, supports all tls.connect options
types?: any, // custom type parsers
statement_timeout?: number, // number of milliseconds before a statement in query will time out, default is no timeout
query_timeout?: number, // number of milliseconds before a query call will timeout, default is no timeout
application_name?: string, // The name of the application that created this Client instance
connectionTimeoutMillis?: number, // number of milliseconds to wait for connection, default is no timeout
idle_in_transaction_session_timeout?: number, // number of milliseconds before terminating any session with an open idle transaction, default is no timeout
};However, this does not use a connection pool, and is therefore less efficient.
It is therefore recommended in most cases not to use msg.pgConfig at all and instead stick to the built-in configuration node.
You can install node-red-contrib-postgresql directly using the editor: Select Manage Palette from the menu (top right), and then select the Install tab in the palette.
You can alternatively install the npm-packaged node:
- Locally within your user data directory (by default,
$HOME/.node-red):
cd $HOME/.node-red
npm i node-red-contrib-postgresql- or globally alongside Node-RED:
npm i -g node-red-contrib-postgresqlYou will then need to restart Node-RED.
This node supports backpressure / flow control: when the Split results option is enabled, it waits for a tick before releasing the next batch of lines, to make sure the rest of your Node-RED flow is ready to process more data (instead of risking an out-of-memory condition), and also conveys this information upstream.
So when the Split results option is enabled, this node will only output one message at first,
and then awaits a message containing a truthy msg.tick before releasing the next message.
To make this behaviour potentially automatic (avoiding manual wires), this node declares its ability by exposing a truthy node.tickConsumer
for downstream nodes to detect this feature, and a truthy node.tickProvider for upstream nodes.
Likewise, this node detects upstream nodes using the same back-pressure convention, and automatically sends ticks.
Example adding a new column in a table, then streaming (split) many lines from that table, batch-updating several lines at a time, then getting a sample consisting of a few lines:
Example: flow.json
The debug nodes illustrate some relevant information to look at.
When the Split results option is enabled (streaming), the messages contain some information following the conventions for messages sequences.
{
payload: '...',
parts: {
id: 0.1234, // sequence ID, randomly generated (changes for every sequence)
index: 5, // incremented for each message of the same sequence
count: 6, // total number of messages; only available in the last message of a sequence
parts: {}, // optional upstream parts information
},
complete: true, // True only for the last message of a sequence
}Major rewrite in July 2021 by Alexandre Alapetite (Alexandra Institute), of parents forks: andreabat / ymedlop / HySoaKa, with inspiration from node-red-contrib-re-postgres (code).
This node builds uppon the node-postgres (pg) library.
Contributions and collaboration welcome.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent