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 1tNJcS-00A8EP-El for pgsql-general@arkaria.postgresql.org; Mon, 16 Dec 2024 22:31:16 +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 1tNJcP-00Bt3g-OL for pgsql-general@arkaria.postgresql.org; Mon, 16 Dec 2024 22:31:14 +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 1tNJcO-00Bt3S-VO for pgsql-general@lists.postgresql.org; Mon, 16 Dec 2024 22:31:14 +0000 Received: from sonic316-21.consmr.mail.ne1.yahoo.com ([66.163.187.147]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tNJcI-003BvO-D5 for pgsql-general@postgresql.org; Mon, 16 Dec 2024 22:31:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1734388264; bh=fnvkgjxbRo7L3bJaAOxkllqS94Of6XPVwhH5MW1iBG8=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=jH8HCkIbk5OFnQb8Tqwozi+8qdYlN8PVB2Dc5CLywaykWGp4rxY/7omLvKDfu3MBIMQx/Ei+ZR3Bm4h/ytKzttdO1WFKviVHeif0Mub0SerhqzazmB2RcYFmIDiQe3m6fnCJQgeT4moPVLmwEXRxS+eK1z+kFX4wc+KOOL6QizOFrMzo2lSl0VrjwPtWmLtkHSjJks78X+RfM7ib+UFyZxtN7AFf92TNisERVmtVKn3SUp0XmhLWN4pPduKAKVjY7mFaFR+hpoDJ2uqyZEsaJxp8L5ZwbKtxd67mx9aw1+OOy7rFPLXPNChqIauUDiTZbFVBTpfESfvSuhK8uZFPwg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1734388264; bh=O6zoi26H3Tcymk8aCvlSefwMi2fngoF9ImMhZnOUQw/=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=mbnpXYOzhZv1vSAifQoKHVfGd/GzCvmfLTQ8xd5txk2VmYfxbDqwG4O2w9HfXWZNGpkF2NoDQp9mERWUM6hpswUsFgmA45jCob6YBw2aKtk/ERRrxEEDbHtYfbKMKWOzM+y7M8J59sF0oQwQjSXh4HB9u8E+gOSolUcLm8olkC+q/yppYypcwvrltiey2zvUu+7Vc9QqfXvA8263P0y6riHVGuLPxRl0hmwhk67xvuyFB/j6etiU/W/8KkPqBeZvebhLmeLNSLhu2SeM39L4mIGm3LTmPX4MYz+jvbDntVhfG7yVgUoUdx7eLlRVeEJlQiMyzr72SZFrk6xdTQ2ijA== X-YMail-OSG: bKdDMqUVM1mTzKViQFSfxC.cnZARA6VedJFFthFQ5l7oThQKirTFK41AOAVQGHE O85Tqqz6qPd2v_wQxGil_19RB2GHRzqGYuy9xCNNyVcHfIMznMCLMFWRKpw59ZaklzD4X58hvB59 YecPyLq1jkyTF3qREao6uNp7VAOhaNz9E.uJgqhpjQKI7oBtuh2.jjwKp2HzWvNzjIRqv1AQ4pJ. XQ01WhbshSUYrUeJpIVYzEDXWBULx3CVVDBZxibKdW2oJcqt3ToPVLixg4OlP_4f0dICglElWAHG 4mZd0nRST2sSV6ultv2T9fx5HJDj_tzZ1HF7H45BRjzaWN9yrMKXHMUc9aXaRNmNxDLrFKUvhM5d NzffJN9abs.RbODaq2mUfAfpc64VKyO2ZPblUqkspWue0StFL26KwSSOZk31RyE4bTSji5uEe_bJ XMaM77CwBeazom1hsfysCDyvrz9VEVxyFgSDyL118.hfCJITdwFq8Kt6SH1oH0mWhpOJ4fzhX5F_ 78UBK_aJMju3S1FFXmmOKi5zYLdXiQ6rGkcIwZZhtMZHBaRiPfha4sEEAZMhiMzRVfTg7TYouyZf kVT1HtGS5IF3UKMv29fFkHq8RhivKehZ5l5QhlqQU64Yg4UkVQ6xQZRWjNN6CuGIpA6OIJtg6Jjj PYBmRJ73rhpc6aGfhl2X05ZBk5KB4xjtsU0RLvpYNtJGRXr6jVG9LJhEcvBk6SbRsEtGsWWgKmit vEqHeIScr5lrBHe45p6ihsc0VkSuO3N_JF3OptV33uXS_jMJ97muW9brEQRdAKUkQuKz_5bIL2JS j8R.pLgmb3ZWFWgtP40D1vhDVUpy2qzMz3F3pnYBK3tvZxim4Vr2MDIgsZvy4QZKznv1L4XcmPfE FF5t2bEBjRYaoZ5TXcVgv8zmHYEvrOs37fBUJxTAo6.jKV_6DyutZRP2K8hjdDHAeesCVRYedLeR 5YikbHwCD7QENoWvR9RXbNwMk4kCYumPljiUMT5x1qustt7irAYELZTuQ1sPiYeNr1Jt2vZxZKS_ l0HLd052rJyK4CK.H_amwAzaJca1VpkWviJ8ErOaJ7_BNw6BZapAH0M0sH4vO3jE6lerSQhjC_Ex rQ4iOdOw_JI8U8w_.on9CF9i4C8MOlnAARIkrNljwxEkVqASKIgknKX4M2PBc7rYU6CtIz4BLUtj AsGJ.9fdKKpHE4rEgxg_sX7ClBWa7bgWybM6TjWIhp6F66uIYBiaNwrwA5mgvZoc6TtqbZs3aLOY YYyjaPas1kkvABG6U69iOw5f4QZ7jHuv5oa7Z5JrE3kXJTTG5cqkvgT2RBgiawOx4h09YPL7EDQD pzfIQYlD1h0BqyuZeDqz1DhSDVsxh_g_1CrbJk5Mpok52ZC8IpZFqo0yLCXSG6wSCnhGNX.oExyq raNAu.BSDdoibWck4ekZ3pFb9Sc6F0sjvp71GBK4YbO29tnZbAZRhsEkLj1Kr.BYJsviuWv5A.Qg Y9aHUA6_nXeQ5hsRX9KyzonnlslJ18DHj67S.3eFVh35HiQU2aLI1wLV80VVRd8_vqm6qgT9GRtB EvxtmrHOtELKZWZcT0G9.CsrCe187Y9e79b.d7tLnl3.LGzyk5efvNHHZNIv9lJreUBtYme0ZHO7 ZiOHsPg8NBOCG6D3tNE54_ZfdyvkGnzd9XH2s4iVOsbT357s0zCnhSgoJSwsi0Vz_l6pj.w7p7Ab cM6hQVKIWnwYKbkLSCrnnShRMKYoQ1d4L7l9kxNsR1e2n40wXfIHG02jFdR2VvLjlEnKsLaXKSs8 MdW0ZLyTM_vAztlxO8I5ztRdnqDyuzNy1Lq6IxYDTx6DzjX4fBjipnJLL2KcQwlLIGM5lWF.TGpK n2ngH1UUrS7FjJ3DDD6vzijdw7bEZMgUswPrnDNj3ZO9b957efx.bQ8xfARRu7nwpEQmJKm5lEFk Tt3KpOQcAx058xHEp0j4HIpH8BmWO8eCDFnufR6.zCEsXHfrrRiCVzaCXdHlk_DfZBNjL2grnWvq qEf7rMe7943rjCiLwB4x7.Ib_h6BNOvjI8CKMV.rd1QERFwGsM3oicQLYXDoFLWip9KxiZb3vDz1 PEmfogQ81WeftdC7Gad502de.mORJG_UsvEBVbgbYK6c8jGplnhMZ9Z627rzmvZep6XPBTgHlf5A 9Z8dUkWVeb4Zgly5OKek5QplYwvEe9MPPZpY_xC4FC6RdMM6EjrTqX_BAMf8jnJ8ohHNohCiK2OE .w5ht3kf_YqdB5gFv6is8i7sNdd4t1AjS3vCSOV3aEE5mUPZE_hraUASrLCeBzVHrDsiXeVlFQCo jJHJsmAf0fe7rAY_FLKTetQZAx10. X-Sonic-MF: X-Sonic-ID: 8655a8a9-d055-4238-85a4-f5c549d51613 Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.ne1.yahoo.com with HTTP; Mon, 16 Dec 2024 22:31:04 +0000 Date: Mon, 16 Dec 2024 22:30:59 +0000 (UTC) From: Bharani SV-forum To: Ron Johnson , pgsql-general , Adrian Klaver Message-ID: <1875422740.4095620.1734388259706@mail.yahoo.com> In-Reply-To: References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.com> <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com> <1061066336.5835157.1733316137292@mail.yahoo.com> <1918413683.2239751.1733944364448@mail.yahoo.com> <037a8338-3434-47d4-aaad-ef186d4d3250@aklaver.com> <101139100.4053671.1734383960480@mail.yahoo.com> Subject: Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4095619_129731283.1734388259704" X-Mailer: WebService/1.1.23040 YMailNorrin Content-Length: 12521 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------=_Part_4095619_129731283.1734388259704 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable a)=C2=A0user =3D=C2=A0postgres b)pg_dump version =3D=C2=A0/usr/bin/pg_dump -V pg_dump (PostgreSQL) 13.16 c) DB version select version () ;=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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0version-----------------------= ---------------------------------------------------------------------------= --------=C2=A0PostgreSQL 13.16 on x86_64-pc-linux-gnu, compiled by gcc (GCC= ) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit use this script for backup pg_dump -Fp -p 5432 -U "$USERNAME" "$DATABASE"=C2=A0 using username =3D postgres for one of the DB (ver 13.16), it worked fine by doing oldvm =3D pg_dump fr= om ver 13.16 andlater restoring in new VM with new OS and new db binary 15.= 09, post creating dummy db (appln related) and restoring the pg_dump from o= ldvm . =20 On Monday, December 16, 2024 at 05:19:31 PM EST, Adrian Klaver wrote: =20 =20 On 12/16/24 13:19, Bharani SV-forum wrote: > Team > I am getting the following error. >=20 > pg_dump: error: error reading large object 2113418: >=20 > pg_dump: error: could not open large object 3391830: What user are you running pg_dump as? What version of pg_dump? >=20 > I tried to give this command DB name =3D abcefg >=20 > ALTER DATABASE abcefgd SET lo_compat_privileges=3Don; >=20 > and reran and once again , i am getting the same error >=20 > while doing using psql/pg_dump from old version server running 13.18 [=20 > OS =3D Amazon Linux release 2 (Karoo) ]. It is either psql or pg_dump. psql is the CLI client for the Postgres=20 server. If you are using psql as an alias for Postgres(sql), don't,=C2=A0 i= t=20 only adds confusion. >=20 > Will be pg_dump and pg_restore to restore in the new VM with new OS [OS= =3D=20 > amazon linux 2023] and new DB bin pgsql ver 15.09. >=20 > We were told by AWS team, in the new VM tagged OS [OS=3D amazon linux=20 > 2023] , pgsql Ver 13.16 is not supported Not sure why? It still a community supported version and will be through=20 November 2025. >=20 > *I cross checked* > SELECT oid, count(*)=C2=A0 FROM pg_largeobject_metadata group by oid orde= r by=20 > oid ; > Rows =3D=C2=A0 4260170 rows >=20 > Can you suggest >=20 >=20 > On Wednesday, December 11, 2024 at 03:57:31 PM EST, Adrian Klaver=20 > wrote: >=20 >=20 > On 12/11/24 11:12, Bharani SV-forum wrote: >=C2=A0 > Team >=C2=A0 > As suggested from old server, post shutdown of DB, I did OS level= dump >=C2=A0 > of PG_DATA folder and had restored in the new server. >=20 > If you follow the process shown here: >=20 > https://www.postgresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA= _TeWMFMRvUM9pXauKg%40mail.gmail.com >=20 > You would not have to do the below. >=20 >=C2=A0 > >=C2=A0 > Any idea on how to install the older binary postgres 13.18 ( OS= =3DAmazon >=C2=A0 > Linux 2023.6.20241121) under a dedicated folder suffixed as the >=C2=A0 > following e.g.) /usr/pgsql1318 >=C2=A0 > >=C2=A0 > System Admin had already installed newer version pgsql 15.08 bina= ries in >=C2=A0 > the=C2=A0 new server (OS=3D Amazon Linux 2023.6.20241121) in the = folder=20 > "/usr/bin/" >=C2=A0 > >=C2=A0 > We were quoted , OS =3D Amazon Linux 2023.6.20241121 doesnot supp= ort >=C2=A0 > postgres ver 15.10 (Community edition) under its AWS-EC2. >=20 > That does not reflect well on Amazon Linux, that it is missing two > critical bug releases. >=20 >=20 >=C2=A0 > >=C2=A0 > Regards >=C2=A0 > >=C2=A0 > >=C2=A0 > >=20 > --=20 > Adrian Klaver > adrian.klaver@aklaver.com >=20 >=20 >=20 --=20 Adrian Klaver adrian.klaver@aklaver.com =20 ------=_Part_4095619_129731283.1734388259704 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
a) 
user =3D 
postgres

b)
pg_dump version =3D 
/usr/bin/pg= _dump -V

pg_dump (PostgreSQL) 13.16

=
c)

DB version

select version () ;
<= div>                    &= nbsp;                    =        version
-----------------------------= ---------------------------------------------------------------------------= --
 PostgreSQL 13.16 on x86_64-pc-linux-gnu, compiled by gcc= (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit

=
use this script for backup

pg_dump -Fp -p 5432 -U "$USERNAME" "$DATABASE" <= /span>

using username =3D postgres
for one of the DB (ver 13.16= ), it worked fine by doing oldvm =3D pg_dump from ver 13.16 and
later restoring in new VM with new OS and = new db binary 15.09, post creating dummy db (appln related) and restoring t= he pg_dump from oldvm .
=20
=20

On Monday, December 16, 2024 at 05:19:31 PM EST, Ad= rian Klaver <adrian.klaver@aklaver.com> wrote:


=20 =20
On 12/16/24 13:19, Bharani SV-forum w= rote:
> Team
> I am getting the f= ollowing error.
>
> pg_dump: err= or: error reading large object 2113418:
>
> pg_dump: error: could not open large object 3391830:

What user are you running pg_dump as?

What version of pg_dump?
>
> I tried to give this command D= B name =3D abcefg
>
> ALTER DATA= BASE abcefgd SET lo_compat_privileges=3Don;
>
> and reran and once again , i am getting the same error
>
> while doing using psql/pg_dump f= rom old version server running 13.18 [
> OS =3D Amazo= n Linux release 2 (Karoo) ].

It is eit= her psql or pg_dump. psql is the CLI client for the Postgres
server. If you are using psql as an alias for Postgres(sql), don't,&nb= sp; it
only adds confusion.

>
> Will be pg_dump and pg_restore to re= store in the new VM with new OS [OS=3D
> amazon linux= 2023] and new DB bin pgsql ver 15.09.
>
> We were told by AWS team, in the new VM tagged OS [OS=3D amazon = linux
> 2023] , pgsql Ver 13.16 is not supported

Not sure why? It still a community support= ed version and will be through
November 2025.

>
> *I cross checked*=
> SELECT oid, count(*)  FROM pg_largeobject_meta= data group by oid order by
> oid ;
= > Rows =3D  4260170 rows
>
= > Can you suggest
>
>
> On Wednesday, December 11, 2024 at 03:57:31 PM EST, Adrian= Klaver
> <adrian.klaver@aklav= er.com> wrote:
>
>
> On 12/11/24 11:12, Bharani SV-forum wrote:
>  > Team
>  > As suggested fro= m old server, post shutdown of DB, I did OS level dump
&g= t;  > of PG_DATA folder and had restored in the new server.
>
> If you follow the process shown her= e:
>
> http= s://www.postgresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA_TeWMF= MRvUM9pXauKg%40mail.gmail.com <https://www.post= gresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA_TeWMFMRvUM9pXauKg= %40mail.gmail.com>
>
> Yo= u would not have to do the below.
>
>  >
>  > Any idea on how to insta= ll the older binary postgres 13.18 ( OS=3DAmazon
>&nbs= p; > Linux 2023.6.20241121) under a dedicated folder suffixed as the
>  > following e.g.) /usr/pgsql1318
>  >
>  > System Admin had alr= eady installed newer version pgsql 15.08 binaries in
>=   > the  new server (OS=3D Amazon Linux 2023.6.20241121) in th= e folder
> "/usr/bin/"
>  &= gt;
>  > We were quoted , OS =3D Amazon Linux = 2023.6.20241121 doesnot support
>  > postgres = ver 15.10 (Community edition) under its AWS-EC2.
> > That does not reflect well on Amazon Linux, that it is= missing two
> critical bug releases.
>
>
>  >
>  > Regards
>  >
>  >
>  >
>
> --
> Adrian Klaver> adrian.klaver@aklaver.com <= ;mailto:adrian.klaver@aklaver.com>

>
&= gt;
>

--
Adrian Klaver
adrian.kla= ver@aklaver.com



------=_Part_4095619_129731283.1734388259704--