Re: pg_upgrade --link - Mailing list pgsql-general

From Adrian Klaver
Subject Re: pg_upgrade --link
Date
Msg-id 0790bbfd-7601-40de-9f59-f5c268c6c2cb@aklaver.com
Whole thread
List 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.klaver@aklaver.com



pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Upgrading 6 versions between 2 systems
Next
From: Laurenz Albe
Date:
Subject: Re: pg_upgrade --link