From: | Dmitry Molotkov <aldarund(at)gmail(dot)com> |
---|---|
To: | andres(at)anarazel(dot)de |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15446: Crash on ALTER TABLE |
Date: | 2018-10-19 23:58:21 |
Message-ID: | CADfhRD+Ee6gzUhAtLcxrenAt-SAt-BiLZ+GzpFWu4=NUQ_z8aQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Hi, that was fast answer, thanks :)
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
сб, 20 окт. 2018 г. в 2:27, Andres Freund <andres(at)anarazel(dot)de>:
> Hi,
>
> On 2018-10-19 23:20:10 +0000, PG Bug reporting form wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference: 15446
> > Logged by: Dmitry Molotkov
> > Email address: aldarund(at)gmail(dot)com
> > PostgreSQL version: 11.0
> > Operating system: docker
> > Description:
> >
> > postgres via docker.
> > latest tag dont work.
> >
> > 2018-10-19 23:17:53.903 UTC [1] LOG: server process (PID 69) was
> terminated
> > by signal 11: Segmentation fault
> > 2018-10-19 23:17:53.903 UTC [1] DETAIL: Failed process was running:
> ALTER
> > TABLE "admin_interface_theme" ALTER COLUMN
> > "related_modal_background_opacity" TYPE varchar(5) USING
> > "related_modal_background_opacity"::varchar(5)
>
> Unfortunately this is not enough information to reproduce the
> problem. It'd be very helpful if you could provide a reproducible set of
> commands that trigger the crash. Alternatively, should that prove hard,
> the very least we're going to need the table definition of that
> admin_interface_theme table, so we can attempt to reproduce the issue
> ourselves.
>
> Greetings,
>
> Andres Freund
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-10-20 00:06:45 | Re: NOTIFY does not work as expected |
Previous Message | Tom Lane | 2018-10-19 23:53:06 | Re: NOTIFY does not work as expected |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2018-10-19 23:59:37 | Re: WAL archive (archive_mode = always) ? |
Previous Message | Andres Freund | 2018-10-19 23:27:02 | Re: BUG #15446: Crash on ALTER TABLE |