Re: Crash when partition column specified twice

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Beena Emerson <memissemerson(at)gmail(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Crash when partition column specified twice
Date: 2017-04-28 17:53:06
Message-ID: CA+TgmoYkgnJwgNTm2UQqy2MrgEhWcj7gyXb_WisB6Vm+og-G=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 28, 2017 at 7:23 AM, Beena Emerson <memissemerson(at)gmail(dot)com> wrote:
> Hello Amit,
>
> The extra n->is_from_type = false; seems to be added by mistake?
>
> @@ -11888,6 +11891,8 @@ TableFuncElement: ColId Typename
> opt_collate_clause
> n->is_local = true;
> n->is_not_null = false;
> n->is_from_type = false;
> + n->is_from_type = false;
> + n->is_from_parent = false;
> n->storage = 0;
> n->raw_default = NULL;
> n->cooked_default = NULL;

Good catch. Committed after fixing that issue.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-04-28 18:03:29 Re: Dropping a partitioned table takes too long
Previous Message Peter Eisentraut 2017-04-28 17:49:47 Re: Interval for launching the table sync worker