Support PostgreSQL (PGv15) to allow PG and YugabyteDB as Database #9831

Activity

1. huly-github-staging commented on Sep 10, 2025

   

   huly-github-stagingBot

   on Sep 10, 2025 – with Huly GitHub Staging

   More actions

   Connected to Huly®: UBERF-13633
3. ghost changed the title [-]PostgreSQL - YugabyteDB instead of CockroachDB[/-] [+]Support PostgreSQL (PGv15) to allow PG and YugabyteDB as Database[/+] on Sep 29, 2025
4. bernatvadell commented on Oct 13, 2025

   

   bernatvadell

   on Oct 13, 2025

   More actions

   I'm interested in the proposal made by @crocinsocks. If necessary, I could help with the implementation/adaptation.

   Reviewing the project, I also saw that a custom adapter could be developed, although I'm not sure how to inject it.

   We just deployed Huly and used the official CockroachDB helm, and we keep getting the error that it doesn't have a license configured, and in the "free" version, telemetry is being sent.
5. DerKnerd commented on Dec 2, 2025

   

   DerKnerd

   on Dec 2, 2025

   More actions

   How is the status on this? I am really interested in Huly, mainly because of integrated test management, but CockroachDB is a very high no go for me.
6. JohnFrrr commented on Dec 20, 2025

   

   JohnFrrr

   on Dec 20, 2025

   More actions

   I'm also interested, just throwing in my two cents: based on the recently added architecture documentations, we can identify which services contact the database and consequently need to be adapted. This will differ on the self-hosted vs Huly Cloud/Enterprise since some features are not available on the self-hosted deployment:

   Self-hosted deployment:

   • Account --> CockroachDB
   • Workspace --> CockroachDB
   • Transactor --> CockroachDB
   • HulyKVS --> CockroachDB
   • Fulltext --> CockroachDB

   Huly Cloud/Enterprise only:

   • Datalake --> CockroachDB
   • Hulylake --> CockroachDB
7. JohnFrrr commented on Jan 12, 2026

   

   JohnFrrr

   on Jan 12, 2026

   More actions

   PostgreSQL support was added in yesterday's release!! #10331
8. crocsinsocks commented on Jan 19, 2026

   

   crocsinsocks

   on Jan 19, 2026

   Last edited by crocsinsocks

   More actions

   @ArtyomSavchenko thought it best to include you as the author of #10331

   I have tried to deploy using the new PostgresSQL support in #10331 with YugabyteDB v2025.2.0.0-b131 (PGv15) and I am getting errors :

   {"level":"info","message":"Worker handshake happened","operation":"all","region":"","source":"workspace","timestamp":"2026-01-19T10:27:07.264Z","version":{"major":0,"minor":7,"patch":343}}
   {"code":"42601","file":"gram.y","hint":"For example, FROM (SELECT ...) [AS] foo.","level":"error","line":"14342","message":"Failed to set account timezone","name":"PostgresError","position":"15","routine":"base_yyparse","severity":"ERROR","severity_local":"ERROR","source":"🤦‍♂️user","timestamp":"2026-01-19T10:27:09.622Z"}
   {"account":"b486cf00-ff1a-46d1-88ea-672bda6cfbc9","email":"*redacted*","level":"info","message":"Confirming email","normalizedEmail":"*redacted*,"source":"🤦‍♂️user","timestamp":"2026-01-19T10:27:44.780Z"}
   {"account":"b486cf00-ff1a-46d1-88ea-672bda6cfbc9","email":"*redacted*,"level":"info","message":"Email confirmed","source":"🤦‍♂️user","timestamp":"2026-01-19T10:27:45.894Z"}
   {"code":"42601","file":"gram.y","hint":"For example, FROM (SELECT ...) [AS] foo.","level":"error","line":"14342","message":"Failed to set account timezone","name":"PostgresError","position":"15","routine":"base_yyparse","severity":"ERROR","severity_local":"ERROR","source":"🤦‍♂️user","timestamp":"2026-01-19T10:27:49.777Z"}
   {"account":"b486cf00-ff1a-46d1-88ea-672bda6cfbc9","level":"info","message":"Creating workspace record","region":"","source":"🤦‍♂️user","timestamp":"2026-01-19T10:28:02.688Z","workspaceName":"test"}
   {"level":"error","message":"Error while processing account method","method":"createWorkspace","origErr":{"code":"42601","file":"gram.y","hint":"For example, FROM (SELECT ...) [AS] foo.","line":"14342","message":"subquery in FROM must have an alias","name":"PostgresError","position":"15","routine":"base_yyparse","severity":"ERROR","severity_local":"ERROR","stack":"PostgresError: subquery in FROM must have an alias\n    at ErrorResponse (/usr/src/app/bundle.js:65663:31)\n    at handle (/usr/src/app/bundle.js:65420:11)\n    at Socket.data (/usr/src/app/bundle.js:65229:13)\n    at Socket.emit (node:events:519:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)"},"source":"🤦‍♂️user","status":{"code":"platform:status:InternalServerError","params":{},"severity":"ERROR"},"timestamp":"2026-01-19T10:28:02.734Z"}
   

   Importantly, the focus is on aliases missing from sub queries: PostgresError: subquery in FROM must have an alias.

   I have had the same error with signup process so this isn't specific to creating a workspace and would seem the pure postgres needs a little more tweaking before it is production ready.

   Very excited to see this moving !

   Thanks

   ps. I am the original author
9. ArtyomSavchenko commented on Jan 19, 2026

   

   ArtyomSavchenko

   on Jan 19, 2026

   Contributor

   More actions

   @crocsinsocks Hey
   I think PostgresSQL 16 should be supported for the main scenarios at this time.
   PostgresSQL 15 and YugabyteDB are not yet fully supported.
   I think we can add support for them soon as well.

   ❤️React with ❤️2Reacted by crocsinsocks and Alex Matthew
10. MichaelUray commented on Oct 20, 2026

    

    MichaelUray

    on Oct 20, 2026

    Contributor

    More actions

    Checked against the current code: plain PostgreSQL is supported as a database backend now, with PostgreSQL-specific account migrations (server/account/src/collections/postgres/migrations.ts) and a pure-Postgres test deployment (tests/docker-compose.purepg.yaml). PG15/YugabyteDB specifics were not verified separately. If maintainers agree, please consider closing.
11. MichaelUray commented on Oct 20, 2026

    

    MichaelUray

    on Oct 20, 2026

    Contributor

    More actions

    @app/ — based on the check described above, this looks resolved in the current code. Could you please close this issue if you agree? If you think it is not fixed yet, please describe what still goes wrong (steps, expected vs. actual behaviour), so it can be looked at again.