From: | Dmitry Molotkov <aldarund(at)gmail(dot)com> |
---|---|
To: | alvherre(at)2ndquadrant(dot)com |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15446: Crash on ALTER TABLE |
Date: | 2018-10-27 10:14:35 |
Message-ID: | CADfhRDKYosWqKg8OV8HwG2iMhbPYJxqPVesOM_cdE=ESKxKi4g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
I just checked with that statement and pgadmin and it still crash the db.
Its not related to my pc, since i initially encountered it on CI with
totally different os and setup, and then reproduced it locally.
https://i.imgur.com/qn1cyOz.png here what happen if i execute that alter
query in pgadmin
сб, 27 окт. 2018 г. в 4:11, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
> On 2018-Oct-27, Dmitry Molotkov wrote:
>
> > Here is query that make it crash
> >
> > BEGIN;
> > --
> > -- Alter field related_modal_background_opacity on theme
> > --
> > ALTER TABLE "admin_interface_theme" ALTER COLUMN
> > "related_modal_background_opacity" TYPE varchar(5) USING
> > "related_modal_background_opacity"::varchar(5);
> > COMMIT;
>
> Hmm, that works fine for me :-( Can't debug further right now ...
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-10-27 14:45:57 | Re: BUG #15446: Crash on ALTER TABLE |
Previous Message | PG Bug reporting form | 2018-10-27 08:54:57 | BUG #15464: I use PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-10-27 10:41:38 | Resetting PGPROC atomics in ProcessInit() |
Previous Message | Heikki Linnakangas | 2018-10-27 10:00:07 | Re: Postgres restore issue |