From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Dmitry Molotkov <aldarund(at)gmail(dot)com> |
Cc: | andres(at)anarazel(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15446: Crash on ALTER TABLE |
Date: | 2018-10-22 17:23:20 |
Message-ID: | 20181022172320.fnau5hxotyobk2st@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 2018-Oct-20, Dmitry Molotkov wrote:
> Reproduce is easy if you can install python 3.
> Here is empty django project that will reproduce it
> https://www.dropbox.com/s/4rw2dlzxvxxb5xf/djangotestpgbug.zip?dl=0
> install requirements from requirements file.
> in djangotestpgbug\settings.py - set postgres user/password/database.
> python manage.py migrate - it will run migration and it will crash
> postgres:latest from docker. Didnt tried without docker. But i dont think
> docker has anything to do with it.
>
> Here is failing migration
> https://github.com/fabiocaccamo/django-admin-interface/blob/master/admin_interface/migrations/0008_change_related_modal_background_opacity_type.py
I think the easiest is to turn DDL logging in the server
(log_statement=ddl) and then report exactly what is being sent to the
server, then see if you can construct a reproducer SQL script based on
that.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-10-22 17:27:58 | Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT |
Previous Message | PG Bug reporting form | 2018-10-22 14:00:50 | BUG #15449: file_fdw using program cause exit code error when using LIMIT |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-10-22 17:27:58 | Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT |
Previous Message | Alvaro Herrera | 2018-10-22 17:19:07 | Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line |