Postgres
Connect & Ingest data from / to a Postgres database
Setup
The following credentials keys are accepted:
host
(required) -> The hostname / ip of the instanceuser
(required) -> The username to access the instancedatabase
(required) -> The database name of the instanceschema
(optional) -> The default schema to usepassword
(optional) -> The password to access the instanceport
(optional) -> The port of the instance. Default is5432
.sslmode
(optional) -> The sslmode of the instance (disable
,allow
,prefer
,require
,verify-ca
orverify-full
). Default isdisable
.ssh_tunnel
(optional) -> The URL of the SSH server you would like to use as a tunnel (examplessh://user:password@db.host:22
)ssh_private_key
(optional) -> The private key to use to access a SSH server (raw string or path to file).ssh_passphrase
(optional) -> The passphrase to use to access a SSH server.
Using sling conns
sling conns
Here are examples of setting a connection named POSTGRES
. We must provide the type=postgres
property:
Environment Variable
Sling Env File YAML
See here to learn more about the sling env.yaml
file.
Database user creation
To allow Sling to access your database, we need to create a user with the proper privileges. Please follow the steps below:
Create a user
sling
(or whatever you prefer) by running:If you are planning to load data into this connection, grant the following privileges to that user:
If you are planning to extract data from this connection, you need to give permission to read the tables you'd like Sling to extract.
If you are facing issues connecting, please reach out to us at support@slingdata.io, on discord or open a Github Issue here.
Last updated