Bug in PostgreSQL 15 : Facing error in PG15

From: Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in>
To: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Bug in PostgreSQL 15 : Facing error in PG15
Date: 2024-08-27 08:44:35
Message-ID: KL1PR0601MB4433AA4BDC279E39281A4F55F0942@KL1PR0601MB4433.apcprd06.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

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.

DB OS RHEL8.

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.

Regards,
Ram Pratap.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2024-08-27 08:46:17 Re: BUG #18589: pg_get_viewdef returns wrong query
Previous Message Thomas Munro 2024-08-27 02:47:29 Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64