Cannot deploy with latest Postgres

Use-case: IdP for personal usage
Environment: Self hosted, deployed with Helm on Kubernetes
Version: latest (Chart 9.13.0, latest tag for Docker image)
Stack:

PostgreSQL 18
Using it in Kubernetes, using Zitadel helm chart and CNPG Operator for PostgreSQL.

What you expected to happen: With a fresh install, by skipping the database creation/grand/user, just to create Zitadel tables.
What went wrong: Running

init zitadel

init zitadel

init zitadel

init zitadel, even with disabled caches, fails on step 34 when creating UNLOGGED tables.
Attachments: More info on the related issue 10712

I'm creating this post because the impact is huge: a new instance cannot be run on latest PostgreSQL version.

Ask Inkeep•12/7/25, 10:31 PM

Hi @Pyrrha, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.

Ask Inkeep•12/7/25, 10:31 PM

Answer

You've identified a known compatibility issue with PostgreSQL 18 (1) . ZITADEL currently supports PostgreSQL versions 14 to 17 (2) , and PostgreSQL 18 is not yet compatible due to changes in how partitioned tables work (1) .

The issue occurs because PostgreSQL 18 no longer allows unlogged partitioned tables, which ZITADEL uses in the cache schema . When starting ZITADEL with PostgreSQL 18, you'll encounter this error:

level=error msg="migration failed" caller=".../cmd/setup/setup.go:373" code=0A000 detail= error="ERROR: partitioned tables cannot be unlogged (SQLSTATE 0A000) "

level=error msg="migration failed" caller=".../cmd/setup/setup.go:373" code=0A000 detail= error="ERROR: partitioned tables cannot be unlogged (SQLSTATE 0A000) "

.

Workaround: Switch to PostgreSQL 17 instead of 18 . Most providers allow you to explicitly choose the PostgreSQL version - for example, with CNPG you can switch to the Postgres 17 image instead of the latest tag .

The ZITADEL team is aware of this issue and is investigating solutions, which may involve rethinking the cache partitioning approach . Until PostgreSQL 18 compatibility is officially added, PostgreSQL 17 is your best option for a fresh installation.

Ask Inkeep•12/7/25, 10:31 PM

To learn more, see the sources I considered:

[1] postgres 18 compatibility
[2] Database Configuration

Ask Inkeep•12/7/25, 10:31 PM

Feel free to tag @Ask Inkeep with additional questions.

Rajat•12/8/25, 11:27 AM

hey @Pyrrha thanks for your qeustion, I have reported internally and I will get back to you on it with more information. Thanks for all the details

Rajat•12/11/25, 11:00 AM

hey @Pyrrha the response from the inkeep is correct acually

Pg18 support was added recently. I think for now, you can version use 17.6 and it should work. Here's the same comment on github

GitHub

postgres 18 compatibility · Issue #10712 · zitadel/zitadel

With postgres 18 it is no longer possible to have unlogged partitioned postgres tables. Zitadel uses them in the cache-schema. We need to rethink these tables before we document postgres 18 compati...