Re: pg_upgrade --link

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Brajendra Pratap Singh <singh(dot)bpratap766(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade --link
Date: 2026-09-15 15:22:13
Message-ID: 0790bbfd-7601-40de-9f59-f5c268c6c2cb@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 9/14/26 6:38 PM, Brajendra Pratap Singh wrote:
> Hi Team,
>
> I have performed the production database upgrade from postgresql 13 to
> 17 version using pg_upgrade --link method on ubuntu 22.04 successfully.

What was the exact complete command you used?

>
> Now after few days of upgrade, while  dropped one database of size 900+
> GB successfully, the space not get reclaimed physically from mount
> point /usr/pgdata.

To be clear you dropped it from 17 server, correct?

>
> Old PG13 data directory: /usr/pgdata/data1 --> size 4.5TB
>
> New PG17 data directory:
> /usr/pgdata/data17 --> 5.6GB
>
> I didn't perform the delete_old_cluster.sh yet.
>
> I can see that the oid of this dropped database is present in PG13 data
> directory base location and occupying 972GB size, while it's not present
> in PG17 data directory base location.
>
> Now my doubt is if I removed Old data directory, will it cause any
> impact on running PG17 cluster.
>
> Please suggest the best and safe approach to reclaim the space.
>
>
> Thank you so much..
>
> Regards,
> BPratap
>

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2026-09-15 20:47:18 Re: pg_upgrade --link
Previous Message Rich Shepard 2026-09-15 12:01:29 Re: Upgrading 6 versions between 2 systems