From: | "Phil Endecott" <spam_from_pgsql_lists(at)chezphil(dot)org> |
---|---|
To: | <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Why can't I drop a tablespace? |
Date: | 2021-07-14 12:17:05 |
Message-ID: | 1626265025382@dmwebmail.dmwebmail.chezphil.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> "Phil Endecott" <spam_from_pgsql_list(at)chezphil(dot)org> writes:
>> Thanks Laurenz. I was looking at the source for "alter table set
>> tablespace" yesterday trying to work out what is supposed to happen.
>> There is a comment at tablecmds.c line 3989: "Thanks to the magic of
>> MVCC, an error anywhere along the way rolls back the whole operation;
>> we don't have to do anything special to clean up." But I guess that
>> creating an entirely new file on a different filesystem is an
>> exception to that.
>
> No, but PANIC'ing during commit is :-(. Ordinarily the files created by a
> failed transaction would be removed during transaction cleanup, but we
> did not reach that code. So these were left behind, but the table's
> original files in the original tablespace should be undamaged.
OK, I've removed them - fingers crossed!
Thanks to everyone who replied for your advice.
Regards, Phil.
From | Date | Subject | |
---|---|---|---|
Next Message | Laura Smith | 2021-07-14 13:18:51 | Re: returning setof from insert ? |
Previous Message | Thomas Kellerer | 2021-07-14 12:14:44 | Re: returning setof from insert ? |