| From: | AP <ap(at)zip(dot)com(dot)au> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15582: ALTER TABLE/INDEX ... SET TABLESPACE does not free disk space |
| Date: | 2019-01-10 10:40:54 |
| Message-ID: | 20190110104053.hxurczmhhuzvopxk@zip.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jan 10, 2019 at 12:44:58PM +0300, Sergei Kornilov wrote:
> Hi
> If archiver can not save WAL - postgresql will not remove these WAL and pg_wal directory will grow unlimited. And i think your alter table set tablespace works ok and table was removed from original disk. But was fully copied to WAL and such WAL can not be deleted, therefore overall disk space usage is same. So you need repair you archive_command first.
Hi,
I just checked. There are only 16GB of WAL in pg_wal. I moved
5.5TB of data so I don't think that that is it.
There are also no errors when I'm not trying to shift an object
to a new tablespace and WAL backups are happening (recent files
in the pgbackrest backup dir).
AP
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-01-10 11:15:45 | BUG #15586: Failed to start PostgreSQL Cluster 10-main |
| Previous Message | Sergei Kornilov | 2019-01-10 09:44:58 | Re: BUG #15582: ALTER TABLE/INDEX ... SET TABLESPACE does not free disk space |