Re: Pre-version pg_upgrade syntax check

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Pre-version pg_upgrade syntax check
Date: 2020-02-11 16:31:10
Message-ID: d212dbb1-23a0-24e5-f9ec-7b26a1bb3a80@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/11/20 5:43 AM, Rich Shepard wrote:
> On Mon, 10 Feb 2020, Adrian Klaver wrote:
>
>> So you already have 11 and 12 instances of Postgres running?
>
> Adrian,
>
> No. Both 11 and 12 are installed; neither is running. I have a cron job
> that
> runs pg_dumpall every weekday night
>
>> If so why use pg_upgrade?
>
> Because I wanted to try it rather than use 'psql -f <filename>.sql'
>
>> To verify what is going on do:
>> /usr/lib64/postgresql/11/bin/psql --version
>
> The pg_upgrade page says to not have either the old or new versions
> running.

The above runs the psql client not the server. It is a way of
determining what version binaries /usr/lib64/postgresql/11/bin/
actually contains.

>
>> vi /var/lib/pgsql/11/data/PG_VERSION
>
> /var/lib/pgsql/11/data/PG_VERSION is 11; /var/lib/pgsql/12/data/PG_VERSION
> is 12.
>
> Rich
>
>

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Catch All 2020-02-11 16:32:19 JIT on Windows with Postgres 12.1
Previous Message Adrian Klaver 2020-02-11 16:27:07 Re: Function not imported in Entity Framework