From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net>, Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Table space not returned to the OS ? |
Date: | 2022-06-27 10:01:41 |
Message-ID: | a12948e8d6c6883cce42ffc6154ea48416770939.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2022-06-27 at 11:38 +0200, Magnus Hagander wrote:
> On Mon, Jun 27, 2022 at 11:30 AM Florents Tselai <florents(dot)tselai(at)gmail(dot)com> wrote:
> > A few months back (October) I had upgraded a Postgres instance from v12 —> 14.
> >
> > The database disk size under /var/lib/postgresql/12 was around 800GB+ back then.
> > Note, that IIRC I had used hard-linking during the upgrade.
> >
> > As I was running out of disk space, I started investigating and found out that
> >
> > /var/lib/postgresql/12/main/base/16385 —> 886GB+
> > /var/lib/postgresql/14 —> 400GB
>
> It looks like you didn't actually delete the old cluster, which you are supposed
> to do once you have verified that the new one works.
I think that it should be done earlier than that, namely immediately after running
pg_upgrade. Once you have started the PostgreSQL 14 server (to verify that it works),
you can no longer use the old cluster.
Yes, the control file is crippled, but in my opinion, the earlier you delete the old
cluster, the safer.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2022-06-27 10:12:53 | Re: Differences in Escaped bytea's when creating a plain pg_dump |
Previous Message | Florents Tselai | 2022-06-27 09:53:06 | Re: Table space not returned to the OS ? |