Re: pg_upgrade

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Загороднев Роман Евгеньевич <re(dot)zagorodnev(at)npff(dot)ru>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_upgrade
Date: 2019-12-31 11:22:30
Message-ID: CAC+AXB0Nc2mn2BYkEJd27bQn+8=uB=Xq3Bs7UkXUwm=m+ZtMEQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Dec 30, 2019 at 12:46 PM Загороднев Роман Евгеньевич <
re(dot)zagorodnev(at)npff(dot)ru> wrote:

>
>
> Fsutil shows only one location:
>
> C:\>fsutil hardlink list C:\PostgreSQL\12\data\base\16410\1249_vm
>
> \PostgreSQL\12\data\base\16410\1249_vm
>
>
>
> C:\>fsutil hardlink list C:\PostgreSQL\12\data\base\16410\113
>
> \PostgreSQL\12\data\base\16410\113
>
>
>

Not every relation is linked during the upgrade, the catalog of the greater
version is new and independent from the older version, as you are testing.

So some overhead is expected, you will need available disk space to fit
that.

Regards,

Juan José Santamaría Flecha

In response to

  • RE: pg_upgrade at 2019-12-30 11:46:05 from Загороднев Роман Евгеньевич

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2019-12-31 19:47:59 Re: A row-level trigger on a partitioned table is not created on a sub-partition created later
Previous Message vignesh C 2019-12-31 06:05:38 Re: Reorderbuffer crash during recovery