Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sirwa-00AMJm-C5 for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 08:52:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sirwX-004CHf-EJ for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 08:52:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sirwW-004CEY-TZ for pgsql-general@lists.postgresql.org; Tue, 27 Aug 2024 08:52:49 +0000 Received: from mail-ua1-x92c.google.com ([2607:f8b0:4864:20::92c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sirwU-001etF-WE for pgsql-general@postgresql.org; Tue, 27 Aug 2024 08:52:48 +0000 Received: by mail-ua1-x92c.google.com with SMTP id a1e0cc1a2514c-844f07f6205so768119241.0 for ; Tue, 27 Aug 2024 01:52:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724748766; x=1725353566; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Th09IiViv9EchVIVcrxG9EGi+PSGkjeBERcv+2QUWto=; b=AmKnmwXtVO0SWWpDcTZFTHSz/XPhtGVbFItv1ZTelz7C2E8QWLD94GUZ4oQHX50FSW zIvfGO0yyEMgbmfx9bLizK+6HEWGBGH7Rl/zQMaMF0NIBdakB4weJN7im615HDk93nRT DG+lx7NvmH46F9EC1aBXhDfJGz0IDzB93O2+wOdwArTystKPD0NjO2+49Q8sfMBAgi9F v1kF85ASk9Fb7WhyL9E6K/j+KLXlo4s9BnXF0/Mu47H/Rs/ozCv+UwIso9PZD4NSzdtr M+lQP40FsUG74ePE2jo9MHhVhbGZqTUIjF4EAcka1cG5jYFh4owujPflH9NtsGO0UjwY qk7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724748766; x=1725353566; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Th09IiViv9EchVIVcrxG9EGi+PSGkjeBERcv+2QUWto=; b=GwQ6P6wI7P4PkaNDHS/nP5EDU3Bfb3BlLwG9Bh6Xx0IjgqbQ+IRA4g/HWI0130p2Zw r89p72HJxeS28vkWiQiPMhIAzSi8NUlgOJ+i+hd8OK5F+aZoXIoTCzCBROVVJZyokku7 usnonILAhnSyqcVmFzOAJlZAJyfFrySGZoIP/JnJJLOFVH+48uJsfNPKxM6+zvXw6Xxd ip3wEcGx8huvzhuxXzcW3H4o/Aar1MFcosOLuAw02ro2syqQomH2Q+8r3qcnz76cbdEp l2Sivu8o9bcxGcnoTJa63OebdHA+nmRaWgApD4cD4YLELp/TCUXaAzF46xT47ERMALEI yt2A== X-Gm-Message-State: AOJu0YxoanmHlUXfQZp4IdjBuXsLUC6Aeu6crqHYfzli5K6O7FCjl0nE TwJllaxGxY0sLg4+6g/D6GdU+ALoJzmzsVvdXu0+eP/09gQnfG8knROHNWYPYPiTd+omuNKk0Z9 DquZat6u4qaXmRQMFnw+z74A3EtM= X-Google-Smtp-Source: AGHT+IHLhk4uu83aUJZx/M6sVg7mbS0ub+AHVJHGzG6U+FekOWwZm3MTldXPHMTrqQ6UGWgYlCqELe7e7nidWJSG79Q= X-Received: by 2002:a05:6122:1d46:b0:4f5:14f9:e12c with SMTP id 71dfb90a1353d-4fd1a8091aemr16380488e0c.13.1724748766033; Tue, 27 Aug 2024 01:52:46 -0700 (PDT) MIME-Version: 1.0 References: <5e94410e-ae0e-db88-24cc-58805a9f73d0@aklaver.com> In-Reply-To: From: Kashif Zeeshan Date: Tue, 27 Aug 2024 13:52:34 +0500 Message-ID: Subject: Re: After DB upgrade from PG13 to PG15 showing error To: Ram Pratap Maurya Cc: "pgsql-general@postgresql.org" Content-Type: multipart/alternative; boundary="00000000000086be460620a65d64" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000086be460620a65d64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi On Tue, Aug 27, 2024 at 1:50=E2=80=AFPM Ram Pratap Maurya < ram.maurya@lavainternational.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. > > > > 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. > --00000000000086be460620a65d64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Tue, Aug 27, 2024 at 1:50=E2=80=AFPM= Ram Pratap Maurya <r= am.maurya@lavainternational.in> wrote:

Dear Team,<= /u>

=C2=A0

We have upgraded PostgreSQL DB from version 13 to 15= version .

We are facing issue in PG15 we not enable any parame= ter related to AUTOVACUUM , but still running on PG15 data base.<= /u>

=C2=A0

Below process showing :

=C2=A0

2313192 | 02:10:01.283176=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 | myLava=C2=A0 | active | autovacuum: VACUUM ANALYZE pub= lic.tstock_movement (to prevent wraparound)

=C2=A0

And one more issue we are facing after upgrade lot o= f alert is coming in DB log file , please suggest this is bug in Postgresql= -15 version.

=C2=A0

2024-08-26 00:00:36.783 IST [702937] WARNIN= G:=C2=A0 oldest xmin is far in the past

2024-08-26 00:00:36.783 IST [702937] HINT:= =C2=A0 Close open transactions soon to avoid wraparound problems.=

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = You might also need to commit or roll back old prepared transactions, or dr= op stale replication slots.

2024-08-26 00:00:36.784 IST [702937] WARNIN= G:=C2=A0 oldest xmin is far in the past

2024-08-26 00:00:36.784 IST [702937] HINT:= =C2=A0 Close open transactions soon to avoid wraparound problems.=

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = You might also need to commit or roll back old prepared transactions, or dr= op stale replication slots.


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

Thanks
Kashif Zeesh= an=C2=A0

=C2=A0

DB =C2=A0OS -RHEL8.

=C2=A0

=C2=A0

Regards,

Ram Pratap.

--00000000000086be460620a65d64--