Falcondevils

I upgraded TimeScaleDB version to 1.19 and also updated the timescaleDB database version to 1.19.0. Then i started upgrading postgres version from 16 to 17. The non TimescaleDB databases go...

I follow the strategy where i don't depend on postgres operator to create the secrets for standby/pooler or super user. I create the secrets before hand before deploying the CRDs....

Thanks

Hi Team, I really need this feature. Can maintainers help to resolve the conflict and merge it?

Minor correction in above ask. The issue occurred after upgrade was done successfully without any error. The issue occurs when I try select query on tables _timescaledb_internal._compressed_hypertable_498/_timescaledb_internal._compressed_hypertable_733/_timescaledb_internal._compressed_hypertable_751

I tried this way also. The issue occurred in 2.15 as well. There is no error while upgrade. Error is after the upgrade when i try direct query on the...

Even though i tried that it does not seem to work. I use external secret operator to create the secrets. External secrets add owner references to the k8 secrets created...

Please help. I am also stuck here

Actually i was able to find a workaround for this. I found in docker failed build that actually it was installing/downloading 3.5.0 version and not 3.4 #21 179.6 Get:26 http://apt.postgresql.org/pub/repos/apt...