public inbox for [email protected]
help / color / mirror / Atom feedAfter DB upgrade from PG13 to PG15 showing error
3+ messages / 3 participants
[nested] [flat]
* After DB upgrade from PG13 to PG15 showing error
@ 2024-08-27 08:50 Ram Pratap Maurya <[email protected]>
2024-08-27 08:52 ` Re: After DB upgrade from PG13 to PG15 showing error Kashif Zeeshan <[email protected]>
2024-08-27 16:13 ` Re: After DB upgrade from PG13 to PG15 showing error Adrian Klaver <[email protected]>
0 siblings, 2 replies; 3+ messages in thread
From: Ram Pratap Maurya @ 2024-08-27 08:50 UTC (permalink / raw)
To: 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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: After DB upgrade from PG13 to PG15 showing error
2024-08-27 08:50 After DB upgrade from PG13 to PG15 showing error Ram Pratap Maurya <[email protected]>
@ 2024-08-27 08:52 ` Kashif Zeeshan <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Kashif Zeeshan @ 2024-08-27 08:52 UTC (permalink / raw)
To: Ram Pratap Maurya <[email protected]>; +Cc: pgsql-general
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.
>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: After DB upgrade from PG13 to PG15 showing error
2024-08-27 08:50 After DB upgrade from PG13 to PG15 showing error Ram Pratap Maurya <[email protected]>
@ 2024-08-27 16:13 ` Adrian Klaver <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Adrian Klaver @ 2024-08-27 16:13 UTC (permalink / raw)
To: Ram Pratap Maurya <[email protected]>; 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
[email protected]
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2024-08-27 16:13 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-08-27 08:50 After DB upgrade from PG13 to PG15 showing error Ram Pratap Maurya <[email protected]>
2024-08-27 08:52 ` Kashif Zeeshan <[email protected]>
2024-08-27 16:13 ` Adrian Klaver <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox