master_copy_shard_placement() ignores DEFAULT PRIVILEGES IN SCHEMA

When I use master_copy_shard_placement() to recover a broken shard, the new shard is created without the default privileges defined in the schema.
In my particular case I am also working with a partitioned table.
As updates to the parent table are coming in during the master_copy_shard_placement() operation, the new shard immediately fails with a permission error.
I can work around the issue by locking the parent table, doing the copy operation, and manually setting the correct permissions. I am running Citusdata 8.1 and postgresql 11.1.