Re: Crashes on a partition whose concurrent detach never finished - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: Crashes on a partition whose concurrent detach never finished
Date
Msg-id CAN4CZFObYJsQ5za=O4kOGXYhKp6Zn9OYVMdBk0zwQWmrZ_7-OA@mail.gmail.com
Whole thread
In response to Re: Crashes on a partition whose concurrent detach never finished  (Nisha Moond <nisha.moond412@gmail.com>)
List pgsql-hackers
> The issue that the 0001 patch you shared is trying to fix is the same
> one reported upthread

Ops, sorry for missing that, I only read the last few messages in the
thread properly and I didn't realize that it was a known issue. I'll
look into that discussion more.

> 2b) For Non-ALL-TABLES publications, the behavior was already correct;
> the change below is a no-op:

Yes, that part was a cosmetic change to make everything follow the
same approach, I don't think it causes any actual issues.



pgsql-hackers by date:

Previous
From: Manu
Date:
Subject: Re: Extension security improvement: Add support for extensions with an owned schema
Next
From: Bharath Rupireddy
Date:
Subject: Re: Teach pg_upgrade to deal with invalid databases