Team
Being dev server, I noticed, we haven't performed analyze/vacuum process.
Noticed and re-triggerred vacuum full and analyze for all the application related db's
Re ran backup.
No issue's appeared during backup.
Not yet performed restoration in pgsql ver 15.09 in new vm with different OS.
Thank you for guiding me
On Monday, December 16, 2024 at 05:49:28 PM EST, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
On 12/16/24 14:30, Bharani SV-forum wrote:
> *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 .
>
That's nice, but the issue is the case that did not work.
What process where you running that caused the error?
> *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 .
>
That's nice, but the issue is the case that did not work.
What process where you running that caused the error?