Search Postgresql Archives

Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



a) 
user = 
postgres

b)
pg_dump version = 
/usr/bin/pg_dump -V

pg_dump (PostgreSQL) 13.16

c)

DB version

select version () ;
                                                 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" 

using username = postgres

for one of the DB (ver 13.16), it worked fine by doing oldvm = 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 the pg_dump from oldvm .

On Monday, December 16, 2024 at 05:19:31 PM EST, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:


On 12/16/24 13:19, Bharani SV-forum wrote:
> Team
> I am getting the following error.
>
> pg_dump: error: 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 DB name = abcefg
>
> ALTER DATABASE abcefgd SET lo_compat_privileges=on;
>
> and reran and once again , i am getting the same error
>
> while doing using psql/pg_dump from old version server running 13.18 [
> OS = Amazon Linux release 2 (Karoo) ].

It is either 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,  it
only adds confusion.

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

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

>
> *I cross checked*
> SELECT oid, count(*)  FROM pg_largeobject_metadata group by oid order by
> oid ;
> Rows =  4260170 rows
>
> Can you suggest
>
>
> On Wednesday, December 11, 2024 at 03:57:31 PM EST, Adrian Klaver
> <adrian.klaver@xxxxxxxxxxx> wrote:
>
>
> On 12/11/24 11:12, Bharani SV-forum wrote:
>  > Team
>  > As suggested from old server, post shutdown of DB, I did OS level dump
>  > of PG_DATA folder and had restored in the new server.
>
> If you follow the process shown here:
>
> https://www.postgresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA_TeWMFMRvUM9pXauKg%40mail.gmail.com <https://www.postgresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA_TeWMFMRvUM9pXauKg%40mail.gmail.com>
>
> You would not have to do the below.
>
>  >
>  > Any idea on how to install the older binary postgres 13.18 ( OS=Amazon
>  > Linux 2023.6.20241121) under a dedicated folder suffixed as the
>  > following e.g.) /usr/pgsql1318
>  >
>  > System Admin had already installed newer version pgsql 15.08 binaries in
>  > the  new server (OS= Amazon Linux 2023.6.20241121) in the folder
> "/usr/bin/"
>  >
>  > We were quoted , OS = 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@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>

>
>
>

--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux