Re: BUG #15446: Crash on ALTER TABLE

On Fri, Jan 4, 2019 at 11:54 PM Dmitry Molotkov <aldarund(at)gmail(dot)com> wrote:

>
> сб, 5 янв. 2019 г. в 01:25, Andres Freund <andres(at)anarazel(dot)de>:
>
>> Hi,
>>
>> Please don't top-quote on postgresql lists.
>>
>> On 2019-01-05 00:46:54 +0300, Dmitry Molotkov wrote:
>> > сб, 5 янв. 2019 г. в 00:17, Andres Freund <andres(at)anarazel(dot)de>:
>> > > On 2019-01-05 00:01:15 +0300, Dmitry Molotkov wrote:
>> > > > That still happens in postgresql 11.1
>> > >
>> > > Well, it's hard for us to fix that problem if we don't have a reliable
>> > > reproducer.
>> > I provided a reliable reproducer that reproduce it in 100% cases. But it
>> > just involve python script..
>>
>> Having to download and run code from dropbox is neither trust-inspiring
>> (I'd
>> have review all the included code before running it), nor low friction...
>> You
>> might get somebody else to distil that down, but in all likelihood it'll
>> take
>> longer. We all have more work than we can handle.
>>
>> Greetings,
>>
>> Andres Freund
>>
>
> Code is pretty much default empty django project with just with added
> package that cause error.
> I can create a github repo if dropbox not trust-inspiring or low friction
> :)
>
>

If all you are running is the django migrations and no other code, you
should be able to use the sqlmigrate command in django to turn it into a
series plain SQL files. Those will make it a lot easier for people here to
reproduce.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>