Re: dropping column prevented due to inherited index
От | Amit Langote |
---|---|
Тема | Re: dropping column prevented due to inherited index |
Дата | |
Msg-id | CA+HiwqE3i+276KO7-WL7k6bC7ikOSbXEXwd4=B9ABTdbLd-i6A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: dropping column prevented due to inherited index (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: dropping column prevented due to inherited index
|
Список | pgsql-hackers |
On Fri, Oct 11, 2019 at 4:16 PM Michael Paquier <michael@paquier.xyz> wrote: > On Thu, Oct 10, 2019 at 05:28:02PM +0900, Amit Langote wrote: > > Actually, the code initializes it on the first call (recursing is > > false) and asserts that it must have been already initialized in a > > recursive (recursing is true) call. > > I have actually kept your simplified version. > > > Okay, sure. Maybe it's better to write the comment inside the if > > block, because if recursing is true, we don't drop yet. > > Sure. > > > Thoughts on suggestion to expand the test case? > > No objections to that, so done as per the attached. Does that match > what you were thinking about? Thanks. The index on b is not really necessary for testing because it remains unaffected, but maybe it's fine. Regards, Amit
В списке pgsql-hackers по дате отправления: