Re: Bug in PostgreSQL 15 : Facing error in PG15

On Tuesday, August 27, 2024, Ram Pratap Maurya <
ram(dot)maurya(at)lavainternational(dot)in> 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.
>
>
>
> *2313192 | 02:10:01.283176 | | myLava | active |
> autovacuum: VACUUM ANALYZE public.tstock_movement (to prevent wraparound)*
>
>
>

Assuming you did disable auto-vacuum then you did this to yourself, not
some bug. It is not possible to turn off the feature as it is designed to
do the anti-wraparound cleanup regardless of any other settings.

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.*
>
>
>
Likewise, your usage patterns of the database are the issue here - these
aren’t bugs, they are a design choice that you need to be aware of and work
within.

David J.