On 10/18/21, 4:56 PM, "Alvaro Herrera" <alvherre@alvh.no-ip.org> wrote:
> Now, what is the worst that can happen if we rename a table under SUE
> and somebody else is using the table concurrently? Is there any way to
> cause a backend crash or something like that? As far as I can see,
> because we grab a fresh catalog snapshot for each query, you can't cause
> anything worse than reading from a different table. I do lack
> imagination for creating attacks, though.
This message [0] in the thread for lowering the lock level for
renaming indexes seems to indicate that there may be some risk of
crashing.
Nathan
[0] https://postgr.es/m/CA%2BTgmobtmFT5g-0dA%3DvEFFtogjRAuDHcYPw%2BqEdou5dZPnF%3Dpg%40mail.gmail.com