Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>
To: n.kalinin@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Date: 2026-05-29T14:23:35Z
Lists: pgsql-bugs
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 only a role with REPLICATION privs can create the replication slot, which as I recall are already pretty powerful.

-- 
Álvaro Herrera



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Disallow direct use of the pgrepack logical decoding plugin