Re: Adding REPACK [concurrently]
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Adding REPACK [concurrently] |
| Дата | |
| Msg-id | 202603161220.7nv6whwu33hi@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: Adding REPACK [concurrently] (Antonin Houska <ah@cybertec.at>) |
| Ответы |
Re: Adding REPACK [concurrently]
|
| Список | pgsql-hackers |
On 2026-Mar-16, Antonin Houska wrote: > One more problem related to the replication slot is that, due to the call of > CheckSlotPermissions() in setup_logical_decoding(), REPLICATION privilege is > required for REPACK (CONCURRENTLY) to run. That's not too user-friendly. > > I think the reason to require the REPLICATION privilege is that, in generic > case, the output plugin can access data of any table in the database. However > REPACK uses one particular plugin and that plugin only decodes changes of one > particular table. Thus I think we don't really need to call > CheckSlotPermissions(). Do I seem to miss something? Yeah, I don't think it makes sense to require REPLICATION privilege to run REPACK. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "Oh, great altar of passive entertainment, bestow upon me thy discordant images at such speed as to render linear thought impossible" (Calvin a la TV)
В списке pgsql-hackers по дате отправления: