On the Coordinator to perform delete table operation
Postgres=# drop table graph. R_credit_info;
Process have been card, see the lock of the Coordinator, found that this statement has got this object AccessExclusiveLock lock
Postgres=# select locktype, pid, base, virtualtransaction, mode, granted the from pg_locks where base='16420';
Locktype | | pid base | virtualtransaction | mode | granted
-- -- -- -- -- -- -- -- -- -- + + -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + -- -- -- -- -- -- -- -- --
Base | 64075 | 16420 | | 97/766 AccessExclusiveLock | t
(row 1)

But are found in more than one datanode have a no pid row-level exclusive lock blocked the DDL statements
Postgres=# select locktype, pid, base, virtualtransaction, mode, granted the from pg_locks where base='16420';
Locktype | | pid base | virtualtransaction | mode | granted
-- -- -- -- -- -- -- -- -- -- + + -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - + -- -- -- -- -- -- -- -- --
Base | 60435 | 16420 | | 141/27963 AccessExclusiveLock | f
Base | | 16420 | | - 1/31739584 RowExclusiveLock | t
(2 rows)
Tried to restart the cluster, the no pid row-level exclusive locks,

This table only for DML operation now, but could not be DDL operations, to solve the great god of all stripes? Online etc.!