Joe Nelson

Moving this out of "Next Up" due to lack of feedback.

* If you need a higher SLA, it’s an option and contact us * Existing language is incorrect in support&billing

On 7/28 @craigkerstiens said (about giving me the details): > Quick note, I've scheduled this to resurface in ~ 5 days and will aim to tackle then.

Given step 2 warns, "do not start the new server," does that remove the danger that the deadlock daemon may be active when the user runs pg_upgrade? (Also the instructions...

(I'm scanning these issues to see which are still relevant, and can confirm that this note still exists in https://docs.citusdata.com/en/v7.3/dist_tables/dml.html#bulk-loading )

Murat's email captures details about this.

The idea is to highlight the features that *do* work vs just the workarounds. We will need to talk with Ozgun / Craig to determine what the most valuable features...

Interestingly there's a comment inside our reference section: ```rst .. Comment out this configuration as currently COPY only support random placement policy. .. citus.shard_placement_policy (enum) $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ ```

This requires more investigation in the code to see where/what it's used for.

Dang, I expected this would be fixed by all the theme work since this issue was created, but nope. I also had suspected it was caused by the terminating semicolons...