QuestDB supports the Postgres wire protocol. As a result, QuestDB is capable of running most of Postgres queries. This means that you can use your favorite Postgres client or driver with QuestDB, at no extra cost.
The storage model used by Postgres is fundamentally different to the one used by QuestDB. Some features that exists for Postgres do not apply to QuestDB.
We provide examples in a number of programming languages. See our "develop" docs for:
#List of supported features
- Querying (all types expect
- Prepared statements with bind parameters (check for specific libraries below)
INSERTstatements with bind parameters
UPDATEstatements with bind parameters
- DDL execution
- Batch inserts with
- Plain authentication
Examples which demonstrate how to use Postgres clients in a number of different languages can be found on the following pages:
- Insert data demonstrates how to use the parameterized queries and prepared statements to insert data.
- Query data shows how to run queries against tables.
- Update data shows how to update tables.
#List of supported connection properties
|qdb||Should be set to any value for example |
|admin||User name configured in |
|quest||Password from |
|-c statement_timeout=60000||The only supported option is |
#List of unsupported features
- Remote file upload (
#Recommended third party tools
The following list of third party tools includes drivers, clients or utility CLIs that our team has tested extensively. Picking an item from it will guarantee that your code will work with QuestDB.
We recognize that our community might value some features more than others. This is why we encourage you to open an issue on GitHub if you think we are missing something important for your workflow.