Closed NitinJadhav-postgres closed 2 years ago
Kindly acknowledge.
Thanks for your report. What's your pglogical version? What's your PostgreSQL version? I bet it is 15. I couldn't reproduce this issue on 14 or earlier. ... poking PostgreSQL code ... Commit postgres/postgres@4eb2176318d includes a signal barrier for DROP DATABASE. pglogical has no logic to handle it in the supervisor code. I think a simple CHECK_FOR_INTERRUPTS might fix it. Another option might be to call a function that handles barrier events.
Thanks for the reply. The pglogical version is 2.4.2 and PostgreSQL version is 15. The analysis and the fix looks good to me.
@eulerto can you tell me when this fix will be released?
Following are the steps to reproduce the issue.
Kindly let me know if I am missing something.