* Chuck Bell <cbell@stripped> [08/08/13 17:07]:
> 2683 Chuck Bell 2008-08-13
> BUG#33414 : Backup: DDL hangs indefinitely if ongoing backup
>
> Added ability to set a timeout for blocked DDL operations. The
> timeout is the number of seconds a blocked DDL operation will
> wait before aborting with an error message. The variable can be
> set only as a session variable.
Don't want to upset the plan, as it looks reasonable in the
current scheme of things, but adding a new option to the server
requires a worklog tasks (this is a feature).
How do you expect the runtime to support this feature when we get
rid of ddl blocker and start using metadata locks for the task?
There will be no "ddl blocker lock" there will be only "metadata
lock on the database". And when taking it, one won't know if the
conflicting lock is from the backup or not, so whether one should
time out or not.
Since metadata locks for all objects are already in, I think the
right solution for this bug is to reassign it to #runtime, which,
in scope of it, will get rid of the DDL blocker (high time it's
been done), introduce generic metadata lock timeouts, and will
start using them.
--
