PostGRESQL Data Driver
Information
Loads point-data from Postgres databases.
The database is expected to be in a one-value-per-row format, as shown in the examples below.
| Driver Info | Detail |
|---|---|
| Driver Type: | History |
| Platforms: | All |
Performance Notes
We suggest you avoid using a relational database for high-speed time series data - unless you're using the Timescale addon.
If you are using an SQL database rather than a dedicated time-series database, you may need to ensure your tables contain appropriate keys.
You should have a key that includes both the Lookup Field and the Date Stamp, and vice-versa. This will make queries significantly faster, particularly if you are querying large amounts of data.
Driver Settings
History drivers have the following options
| Option | Description |
|---|---|
| Host | The IP address or host name of your MSSQL server |
| Port | The TCP port to connect to |
| Database | The name of the MySQL database |
| Username | The username to login as. Must have read access to the table. |
| Password | The password to go with the username above |
| Table | The database table to query |
| Lookup Field | The field that contains the point name |
| Date Stamp | The field that contains the timestamp for the record (optional) |
| Value | The field that contains the value for the record |
| Filter | An SQL filter you might want to add to the query (optional) |
| Date Format | The format the date is stored/communicated in. Almost always 'Timestamp' |
| Date Distribution | See the section on Scattered vs Synchronised Data Sources |
| Timezone | The timezone all date stamps are stored in |