public inbox for [email protected]  

help / color / mirror / Atom feed

From: Kashif Zeeshan <[email protected]>
To: Ram Pratap Maurya <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: After DB upgrade from PG13 to PG15 showing error
Date: Tue, 27 Aug 2024 13:52:34 +0500
Message-ID: <CAAPsdhdBx+c1-9k+sOvjc4TuZsLEgPnfHOsnipb_E-M3=8E76A@mail.gmail.com> (raw)
In-Reply-To: <KL1PR0601MB4433A16CA91281FA92612A70F0942@KL1PR0601MB4433.apcprd06.prod.outlook.com>
References: <KL1PR0601MB4433D6A72DE1CA03D9D6F75DF0F39@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<[email protected]>
	<KL1PR0601MB443325E8306395D5428BAC04F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<KL1PR0601MB44331424CA913E84AAEB9087F0F29@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<KL1PR0601MB44337E6BE959E78CEB3D1D0BF03FA@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<KL1PR0601MB4433A16CA91281FA92612A70F0942@KL1PR0601MB4433.apcprd06.prod.outlook.com>

Hi

On Tue, Aug 27, 2024 at 1:50 PM Ram Pratap Maurya <
[email protected]> wrote:

> 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.*
>

These are warnings not error, can you please share the error you are
getting.

Thanks
Kashif Zeeshan

>
>
> *DB  OS -RHEL8.*
>
>
>
>
>
> Regards,
>
> Ram Pratap.
>

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: After DB upgrade from PG13 to PG15 showing error
  In-Reply-To: <CAAPsdhdBx+c1-9k+sOvjc4TuZsLEgPnfHOsnipb_E-M3=8E76A@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox