Hi, On 2026-02-15 18:18:30 +0100, Matthias van de Meent wrote: > However, with the current code, the DBA can't make the choice whether > to allow logical replication or not, at least not without reverting to > wal_level=minimal -- which removes effectively all HA features. No > amount of monitoring or rights management can make a DBA safely use > the features enabled by wal_level=replica without risking additional > overhead with effective_wal_level=logical; a very significant change > from PG versions up to 18, where you could safely run your server like > that.
I really don't understand this argument. If you are worried about WAL volume: Any user with rights to create a table or do DML can increase WAL volume to an arbitrary degree. And that's actually harder to pinpoint than seeing that a new replication slot has been created, since the user creating a lot of WAL with a new table can do so in a transaction that creates and drops the table, thereby never having any visible stats. What is the realistic scenario in which you trust a user enough to have REPLICATION rights, i.e. a right to read *all* data in the server *and* to hold back horizons arbitrarily far, but you are worried about them creating logical replication slots? I don't think it exists. Greetings, Andres Freund
