Re: After DB upgrade from PG13 to PG15 showing error - Mailing list pgsql-general

From Adrian Klaver
Subject Re: After DB upgrade from PG13 to PG15 showing error
Date
Msg-id fa535950-669c-46c3-af0c-8169912e11aa@aklaver.com
Whole thread Raw
In response to After DB upgrade from PG13 to PG15 showing error  (Ram Pratap Maurya <ram.maurya@lavainternational.in>)
List pgsql-general
On 8/27/24 01:50, Ram Pratap Maurya 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.

You need to provide more detail about the above.

What parameters are you trying to change?

Do you get an error?

Did you reload/restart the server after the changes?

What user did you do the changes as?



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

I would say the above is pointing you at possible solutions.

To understand why this is important:

https://www.postgresql.org/docs/16/routine-vacuuming.html

Read the following sections:

25.1.5. Preventing Transaction ID Wraparound Failures

25.1.6. The Autovacuum Daemon

> 
> Regards,
> 
> Ram Pratap.
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Using PQsocketPoll() for PIPELINE mode
Next
From: Adrian Klaver
Date:
Subject: Re: Strange behaviors with ranges