Re: [HACKERS] Crash when partition column specified twice - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Crash when partition column specified twice
Date
Msg-id CA+TgmoYkgnJwgNTm2UQqy2MrgEhWcj7gyXb_WisB6Vm+og-G=Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Crash when partition column specified twice  (Beena Emerson <memissemerson@gmail.com>)
Responses Re: [HACKERS] Crash when partition column specified twice  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On Fri, Apr 28, 2017 at 7:23 AM, Beena Emerson <memissemerson@gmail.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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Interval for launching the table sync worker
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Dropping a partitioned table takes too long