Right, so your experience was that the dba team wasn't an enabling team but instead a complicated subsystem team. I would argue, and you seem to agree, that str

Right, so your experience was that the dba team wasn't an enabling team but instead a complicated subsystem team. I would argue, and you seem to agree, that streams need to own their own database, some dbas don't want that and they get caught up performing all the toil on the databases instead of solving just the interesting problems that require their skillset. Yes, these things happen. You should be calling the dbas in (for example) when you need help configuring autovacuums because you have so much load on the db during ordinary operations that a poorly timed autovacuum can cause massive service disruption. Inevitably, some banks will come to view their accounting database as a complicated subsystem in and of itself possibly to the chagrin of the accounting application engineers. A DBA performing execution of an index migration is usually not a good use of their expertise.