Prev: [HACKERS] Upgrade procedure for 9.0 with HS/SR ... ?
Next: [HACKERS] deprecating =>, take two
From: Guillaume Lelarge on 21 Jun 2010 12:46
Hi,

Today, I tried to cancel the change of a tablespace for a table (ALTER
TABLE ... SET TABLESPACE). I got the "Cancel request sent" but the query
continued and finally succeed. It was a big issue for my customer, and I
wanted to look more into that issue. So, I got a look at the source code
and found we didn't check for interrupts in this part of the code. I
added them, and it seems to work as I wanted.

I added a CHECK_FOR_INTERRUPTS call in the copy_relation_data(),
copy_dir(), and copy_file() functions. Works for me on ALTER TABLE ...
SET TABLESPACE and ALTER DATABASE ... SET TABLESPACE, in 9.0 and 8.4.

Not sure we really want that change, and it don't feel like a bug to me.
Should I add it to to the next commitfest?

Comments?


--
Guillaume
http://www.postgresql.fr
http://dalibo.com
 | 
Pages: 1
Prev: [HACKERS] Upgrade procedure for 9.0 with HS/SR ... ?
Next: [HACKERS] deprecating =>, take two