Re: Crash when partition column specified twice
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Beena Emerson <memissemerson@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-04-28T17:53:06Z
Lists: 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
Commits
-
Fix crash when partitioned column specified twice.
- 504c2205abc7 10.0 landed