From: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in> |
---|---|
To: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | After DB upgrade from PG13 to PG15 showing error |
Date: | 2024-08-27 08:50:36 |
Message-ID: | KL1PR0601MB4433A16CA91281FA92612A70F0942@KL1PR0601MB4433.apcprd06.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Dear Team,
We have upgraded PostgreSQL DB from version 13 to 15 version .
We are facing issue in PG15 we not enable any parameter related to AUTOVACUUM , but still running on PG15 data base.
Below process showing :
2313192 | 02:10:01.283176 | | myLava | active | autovacuum: VACUUM ANALYZE public.tstock_movement (to prevent wraparound)
And one more issue we are facing after upgrade lot of alert is coming in DB log file , please suggest this is bug in Postgresql-15 version.
2024-08-26 00:00:36.783 IST [702937] WARNING: oldest xmin is far in the past
2024-08-26 00:00:36.783 IST [702937] 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.
2024-08-26 00:00:36.784 IST [702937] WARNING: oldest xmin is far in the past
2024-08-26 00:00:36.784 IST [702937] 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.
DB OS -RHEL8.
Regards,
Ram Pratap.
From | Date | Subject | |
---|---|---|---|
Next Message | Kashif Zeeshan | 2024-08-27 08:52:34 | Re: After DB upgrade from PG13 to PG15 showing error |
Previous Message | Wim Bertels | 2024-08-27 08:49:32 | Re: Unexpected authentication behaviour |
From | Date | Subject | |
---|---|---|---|
Next Message | Kashif Zeeshan | 2024-08-27 08:52:34 | Re: After DB upgrade from PG13 to PG15 showing error |
Previous Message | Avi Weinberg | 2024-08-27 06:53:42 | logical replication - who is managing replication slots created automatically during initial sync |