On Fri, May 3, 2024 at 4:23 PM Justin Pryzby <pry...@telsasoft.com> wrote: > On Wed, May 01, 2024 at 10:51:24PM +0300, Dmitry Koval wrote: > > 30.04.2024 23:15, Justin Pryzby пишет: > > > Is this issue already fixed ? > > > I wasn't able to reproduce it. Maybe it only happened with earlier > > > patch versions applied ? > > > > I think this was fixed in commit [1]. > > > > [1] > > https://github.com/postgres/postgres/commit/fcf80c5d5f0f3787e70fca8fd029d2e08a923f91 > > I tried to reproduce it at fcf80c5d5f~, but couldn't. > I don't see how that patch would fix it anyway. > I'm hoping Alexander can confirm what happened.
This problem is only relevant for an old version of fix [1], which overrides schemas for new partitions. That version was never committed. > The other remaining issues I'm aware of are for EXCLUDING STATISTICS and > refusing to ALTER if the owners don't match. These two are in my list. I'm planning to work on them in the next few days. > Note that the error that led to "EXCLUDING IDENTITY" is being discused > over here: > https://www.postgresql.org/message-id/3b8a9dc1-bbc7-0ef5-6863-c432afac7...@gmail.com > > It's possible that once that's addressed, the exclusion should be > removed here, too. +1 Links. 1. https://www.postgresql.org/message-id/edfbd846-dcc1-42d1-ac26-715691b687d3%40postgrespro.ru ------ Regards, Alexander Korotkov Supabase
