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: | 2019-01-04 21:01:15 |
Message-ID: | CADfhRDLaB4T-oGJujgpcDb05Q3cs0cuUws7UWGqkxR761T5Tpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
That still happens in postgresql 11.1
сб, 27 окт. 2018 г. в 18:39, Dmitry Molotkov <aldarund(at)gmail(dot)com>:
> I tried to reproduce it with DDL but no luck. I even tried to backup with
> the state before crash and then restore but there wasn't error in such case
> too.
> I`m using windows, so i cant really follow your instruction for taking
> dump.
> I guess the easiest would be to recreate it via that python .
>
> сб, 27 окт. 2018 г. в 17:46, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
>
>> On 2018-Oct-27, Dmitry Molotkov wrote:
>>
>> > 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
>>
>> It probably depends on other things in the table -- maybe indexes, or
>> foreign keys, or something else. If you can reproduce in psql or
>> pgadmin starting from an empty database and some DDL, please submit
>> that.
>>
>> If not, can you attach a debugger to the process before it crashes, and
>> get a core file? There are some instructions here:
>>
>> https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
>>
>> Thanks
>>
>> --
>> Álvaro Herrera https://www.2ndQuadrant.com/
>> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-01-04 21:14:03 | Re: BUG #15575: Using RDS upgrade option from 9.6 to 10.4 Upsert will not insert records but complete successfully |
Previous Message | PG Bug reporting form | 2019-01-04 20:31:10 | BUG #15575: Using RDS upgrade option from 9.6 to 10.4 Upsert will not insert records but complete successfully |
From | Date | Subject | |
---|---|---|---|
Next Message | Joerg Sonnenberger | 2019-01-04 21:10:03 | Re: reducing the footprint of ScanKeyword (was Re: Large writable variables) |
Previous Message | John Naylor | 2019-01-04 20:46:32 | Re: reducing the footprint of ScanKeyword (was Re: Large writable variables) |