On Thu, Dec 9, 2021 at 7:23 PM Neha Sharma <neha.sha...@enterprisedb.com> wrote: > > On Thu, Dec 9, 2021 at 11:12 AM Ashutosh Sharma <ashu.coe...@gmail.com> wrote:
> \c postgres > alter database test1 set tablespace tab1; > > --Cancel the below command after few seconds > alter database test1 set tablespace pg_default; > > \c test1 > alter table t set tablespace tab1; > > > Logfile Snippet: > 2021-12-09 17:49:18.110 +04 [18151] PANIC: could not fsync file > "base/116398/116400": No such file or directory > 2021-12-09 17:49:19.105 +04 [18150] LOG: checkpointer process (PID 18151) > was terminated by signal 6: Aborted > 2021-12-09 17:49:19.105 +04 [18150] LOG: terminating any other active server > processes Yeah, it seems like the fsync requests produced while copying database objects to the new tablespace are not unregistered. This seems like a different issue than previously raised. I will work on this next week, thanks for testing. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com