Database admin -- 2

I have an issue with timescale db

1. From db logs hosted in kubernetes env

WARNING: oldest multixact is far in the past

HINT: Close open transactions with multixacts soon to avoid wraparound problems.

WARNING: oldest xmin is far in the past

HINT: Close open transactions soon to avoid wraparound problems.

You might also need to commit or roll back old prepared transactions, or drop stale replication slots.

2 when querying one table or vacuuming this table called features in the db, can query other tables

ERROR: [data-timescale-data-2]: multixact "members" limit exceeded

SQL state: 54000

Detail: This command would create a multixact with 15 members, but the remaining space is only enough for 0 members.

Hint: Execute a database-wide VACUUM in database with OID 16384 with reduced vacuum_multixact_freeze_min_age and vacuum_multixact_freeze_table_age settings.

I don’t have recent backup and cannot afford to loose data, can you help resolve it?

Synopsis -

We have a timescaledb that internally uses postgres12.7. It is running on a kubernetes cluster hosted in AWS. We used helm to deploy this Db. I am connected currently to it through pdadmin4. This db has 5 tables, i am able to query all the tables but one. When i query that table, it gives me an error 2 (multixact "members" limit exceeded)

When i check the logs of the db i.e container logs i see error 1. There are 3 replicas i.e three pods running. Two pods are throwing error 1.

i have tried vacuum it but was unsuccesful, unable to understand how to resolve this issue

i need help recovering this table and adjust parameters that will suit the db, that way we can continue our normal operations. Right now, i have disabled any data flow into the db. So taking downtime, cannot afford it

SQL Database Administration Relational Databases PostgreSQL Administration Database Management

Project ID: #37336858

About the project