feat: Add support for the PostgreSQL connector (#883)

* feat: Add support for the PostgreSQL connector

* changelog

* Use to_uppercase

* typo

Author: sbernauer

CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+### Added
+
+- Added support for the [PostgreSQL connector](https://trino.io/docs/current/connector/postgresql.html) using the new generic database connection mechanism.
+  Previously, users had to use the `generic` connector ([#883]).
+
 ### Changed
 
 - BREAKING: `configOverrides` now only accepts the supported config file names
@@ -26,6 +31,7 @@ All notable changes to this project will be documented in this file.
 [#869]: https://github.com/stackabletech/trino-operator/pull/869
 [#876]: https://github.com/stackabletech/trino-operator/pull/876
 [#878]: https://github.com/stackabletech/trino-operator/pull/878
+[#883]: https://github.com/stackabletech/trino-operator/pull/883
 
 ## [26.3.0] - 2026-03-16
 

Cargo.nix

@@ -4,6 +4,7 @@ Primarily the https://trino.io/docs/current/connector/blackhole.html[Black Hole
 It works like the `/dev/null` device on Unix-like operating systems for data writing and like `/dev/null` or `/dev/zero` for data reading.
 
 == Example Black Hole catalog configuration
+
 [source,yaml]
 ----
 apiVersion: trino.stackable.tech/v1alpha1

crate-hashes.json

@@ -30,5 +30,6 @@ spec:
 ----
 
 == Connect to S3 store or HDFS
+
 The Delta Lake connector connects to S3 or HDFS in the same way the xref:usage-guide/catalogs/hive.adoc[] connector does.
 Refer to that documentation for access configuration.

docs/modules/trino/pages/usage-guide/catalogs/black-hole.adoc

@@ -8,6 +8,7 @@ In case the Stackable operator for Trino does not support a specific connector y
 This is how you can e.g. use the {trino-psql-connector}[PostgreSQL connector]:
 
 == Example generic catalog properties
+
 [source,yaml]
 ----
 apiVersion: trino.stackable.tech/v1alpha1

docs/modules/trino/pages/usage-guide/catalogs/delta-lake.adoc

@@ -6,6 +6,7 @@ It needs a service-user to access the Google APIs.
 Consult the {trino-google-sheets-connector}[official documentation] on how to use the Google Sheets connector.
 
 == Example Google sheets catalog configuration
+
 [source,yaml]
 ----
 apiVersion: trino.stackable.tech/v1alpha1

docs/modules/trino/pages/usage-guide/catalogs/generic.adoc

@@ -5,6 +5,7 @@ The Apache Hive connector allows Trino to connect to a Hive metastore and query
 Deploy a Hive Stacklet with the xref:hive:index.adoc[].
 
 == Example Hive catalog configuration
+
 [source,yaml]
 ----
 apiVersion: trino.stackable.tech/v1alpha1
@@ -34,6 +35,7 @@ spec:
 <4> Use `configOverrides` to add arbitrary properties to the Trino catalog configuration
 
 == Connect to S3 store
+
 The Hive connector can connect to an S3 store as follows:
 
 [source,yaml]
@@ -58,6 +60,7 @@ See xref:concepts:s3.adoc[] for details about S3 connections.
 IMPORTANT: Make sure that the underlying Hive metastore also has access to the S3 store, because it will e.g. check if the directory exists when creating tables.
 
 == Connect to HDFS cluster
+
 The hive connector can connect to an HDFS operated by Stackable as follows:
 
 [source,yaml]
@@ -72,10 +75,12 @@ spec:
 IMPORTANT: Make sure that the underlying Hive metastore also has access to the HDFS, because it will e.g. check if the directory exists when creating tables.
 
 == Adding unmanaged Hive clusters
+
 You can add connect Trino to Hive catalogs from systems that are not managed by Stackable, including Hive running on existing Hadoop clusters.
 Unmanaged Hive instances can be defined by creating a ConfigMap containing the configuration for the remote Hive Metastore and HDFS or S3 storage services.
 
 === Create a Hive Metastore configMap
+
 The Hive metastore ConfigMap contains the URL for the metastore's thrift endpoint.
 [source,yaml]
 ----
@@ -88,6 +93,7 @@ data:
 ----
 
 === Create a HDFS configMap
+
 When the Hive data is stored on HDFS you will need to provide a ConfigMap containing the HDFS configuration.
 To do this take the `core-site.xml` and `hdfs-site.xml` from your Hadoop cluster and create a ConfigMap with the keys `core-site.xml` and `hdfs-site.xml`.
 
@@ -119,6 +125,7 @@ data:
 ----
 
 === Create the Trino Hive catalog
+
 To use the unmanaged Hive metastore we define a TrinoCatalog object in the same way we would for a managed cluster, referencing the custom ConfigMap we created for Hive and HDFS.
 
 [source,yaml]

docs/modules/trino/pages/usage-guide/catalogs/google-sheets.adoc

@@ -4,6 +4,7 @@ Trino does not have a built-in catalog and instead provides connectors to extern
 This allows Trino to connect to, read from and join a wide variety of data sources.
 
 == Using catalogs
+
 Catalogs are defined in their own resources and referenced from cluster objects.
 See the xref:concepts.adoc[] page for more details.
 

docs/modules/trino/pages/usage-guide/catalogs/hive.adoc

@@ -0,0 +1,32 @@
+= PostgreSQL
+
+The https://trino.io/docs/current/connector/postgresql.html[PostgreSQL connector] provides connectivity to a PostgreSQL databases.
+
+== Example PostgreSQL catalog configuration
+
+[source,yaml]
+----
+apiVersion: trino.stackable.tech/v1alpha1
+kind: TrinoCatalog
+metadata:
+  # The name of the catalog as it will appear in Trino
+  name: postgresql
+  # TrinoCluster can use these labels to select which catalogs to include
+  labels:
+    trino: simple-trino
+spec:
+  connector:
+    postgresql:
+      host: my-postgresql
+      port: 5432 # defaults to 5432
+      database: mydatabase
+      credentialsSecretName: my-postgresql-credentials # Must provide the username and password keys
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  name: my-postgresql-credentials
+stringData:
+  username: myusername
+  password: mypassword
+----