Hi,
On 2026-05-28, PG Bug reporting form wrote:
> It appears that the pgrepack output plugin is accessible through the SQL
> logical decoding API, even though the plugin code explicitly indicates that
> this interface is not supported. Reading changes from such a slot can cause
> a backend process crash in builds with asserts enabled.
> Is this considered normal behavior for the pgrepack plugin, i.e. essentially
> a “don’t do that” situation?
Yeah, I would like to have a way to prevent this, if only for user-friendliness, but it's not terribly pressing since
onlya role with REPLICATION privs can create the replication slot, which as I recall are already pretty powerful.
--
Álvaro Herrera
