From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Subject: | Re: BUG #15684: Server crash on DROP partitioned table |
Date: | 2019-03-10 19:15:21 |
Message-ID: | 19cd0291-67de-e7d6-9565-7878514b733b@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello Julien,
10.03.2019 22:04, Julien Rouhaud wrote:
> Hi,
>
> On Sun, Mar 10, 2019 at 7:55 PM PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
>> The following query:
>> create table at_partitioned (a int, b text) partition by range (a);
>> create table at_part_1 partition of at_partitioned for values from (0) to
>> (1000);
>> create table at_part_2 partition of at_partitioned for values from (1000) to
>> (2000);
>> create index on at_partitioned (b);
>> alter table at_partitioned alter column b type numeric using b::numeric;
>> alter table at_partitioned alter column b type numeric using b::numeric;
>> drop table at_partitioned cascade;
>>
> It seems to be the same bug as described in bug #15672
> (/message-id/15672-b9fa7db32698269f@postgresql.org)
> I'm Cc-ing Amit just in case.
Yes, after applying the patch presented in that thread the crash is not
reproduced.
Thanks for the tip!
Best regards,
Alexander
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2019-03-11 00:32:46 | Re: BUG #15684: Server crash on DROP partitioned table |
Previous Message | Julien Rouhaud | 2019-03-10 19:04:59 | Re: BUG #15684: Server crash on DROP partitioned table |