This seems to be problematic in several compliance schemes. Most will make sure developers,QA etc. do not get access to production data.
All that said it's helpful feedback and something we could definitely look at building more into the product.
if you use Heroku Postgres Database ( production tier ), they have a fork feature as well.
if you are running Postgres on your own and for relatively small loads, it's quite trivial to create a copy of the db using Template
CREATE DATABASE new_db TEMPLATE = old_db;
While not the responsibility of a DB vendor, it would be nice if this includes some Data anonymization/randomization option.
Fully agreed on the data anonymization, and it's something we'll think about in the future. Prior to Citus I ran product for Heroku Postgres for a number of years and the engineering team behind our database as a service is the early team that also built Heroku Postgres so it's much of the same product we aimed to create here. Anonymization absolutely makes sense we just have to figure out the right way to deliver it.
Docker-compose and a makefile make it all very straightforward.