Re: Getting error while upgrading postgres from version 12 to 13

On 3/21/23 08:13, shashidhar Reddy wrote:
> Both shows different versions as 13 shows version 13.10 and 12 shows 12.
The question asked was:

"Check the value that is the PG_VERSION file in each data directory. It
should be 12 in /usr/pgdata/pg_data and 13 in /usr/pgdata/pg_data2."

So indicate which directory path has which PG_VERSION value.

While you are at it do:

/usr/lib/postgresql/13/bin/pg_upgrade -V

and post the version returned.

>
> On Tue, 21 Mar, 2023, 8:09 pm Adrian Klaver, <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> On 3/21/23 03:29, shashidhar Reddy wrote:
> > Actually I was using the below command to check the
> compatibility, it
> > worked without any issue with 12.6 but it is not working with
> 1version 2.14
> > time /usr/lib/postgresql/13/bin/pg_upgrade --old-bindir
> > /usr/lib/postgresql/12/bin --new-bindir /usr/lib/postgresql/13/bin
> > --old-datadir /usr/pgdata/pg_data --new-datadir /usr/pgdata/pg_data2
> > --link --check
> >
> > I have used a different directory for postgres13 from postgres 12.
>
> The issue is not that they are the same directory it is:
>
> FATAL:  database files are incompatible with server
>   DETAIL:  The data directory was initialized by PostgreSQL version 13
> , which is not compatible with this version 12.14 (Ubuntu
> 12.14-1.pgdg18.04+1)
>
> Check the value that is the PG_VERSION file in each data directory. It
> should be 12 in /usr/pgdata/pg_data  and 13 in /usr/pgdata/pg_data2.
>
> >
> > On Mon, Mar 20, 2023 at 11:07 AM <abdulsayeed24(at)gmail(dot)com
> <mailto:abdulsayeed24(at)gmail(dot)com>
> > <mailto:abdulsayeed24(at)gmail(dot)com
> <mailto:abdulsayeed24(at)gmail(dot)com>>> wrote:
> >
> >     Hello,
> >
> >     As per error it seems you have initiated source data with PG13
> >     binaries.
> >
> >     Could you please connect to both source and target psql and share
> >     out of select versions();
> >
> >     Also share pg_upgrade complete command which you are using.
> >
> >
> >
> >     Regards,
> >     Abdul Sayeed
> >
> >
> >
> >     Sent from myMail for iOS
> >
> >
> >     Sunday, 19 March 2023 at 11:29 AM +0530 from
> > david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>
> <mailto:david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>>
> >     <david(dot)g(dot)johnston(at)gmail(dot)com
> <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>
> <mailto:david(dot)g(dot)johnston(at)gmail(dot)com
> <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>>>:
> >
> >         On Sat, Mar 18, 2023 at 7:27PM shashidhar Reddy
> >         <shashidharreddy001(at)gmail(dot)com
> <mailto:shashidharreddy001(at)gmail(dot)com>
> >         <mailto:shashidharreddy001(at)gmail(dot)com
> <mailto:shashidharreddy001(at)gmail(dot)com>>> wrote:
> >
> >             Can someone please help me with this?
> >
> >
> >
> >         You haven't given others enough information to help you.
> >         Present to the fullest extent possible your current
> environment
> >         and the commands you are running.  Showing that psql itself
> >         works on both running clusters would be a good start.  Show
> >         inputs, not just outputs those inputs creates.
> >
> >         David J.
> >
> >
> >
> > --
> > Shashidhar
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com