Re: pg_upgrade as a way of cloning an instance?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Luca Ferrari <fluca1978(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade as a way of cloning an instance?
Date: 2021-07-08 00:30:51
Message-ID: 20210708003051.GA1173@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 7, 2021 at 10:30:15AM +0200, Luca Ferrari wrote:
> On Wed, Jul 7, 2021 at 10:22 AM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> > Yeah, seems pretty pointless. You can just copy the data directory
> > directly and get the same effect. pg_upgrade basically does a data
> > directory copy plus some extra stuff to convert the system catalogs
> > between versions, and if you don't need that second part, you might as
> > well do the first part directly.
>
>
> Agree on everything, but I was curious, since users sometime find ways
> to do things that are almost insane!

Also, pg_upgrade will throw an error if copying from one version to the
same version if there are tablespaces since the tablespace directory
name is the catalog version name.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message 管竚 2021-07-08 03:15:36 Re: Does psqlodbc_10_03_0000-x86(32bit) support PostgreSQL 12.664bit?
Previous Message Merlin Moncure 2021-07-07 21:39:52 Re: Doubt on pgbouncer