Re: BUG #15198: nextval() accepts tables/indexes when adding a default to a column

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Feike Steenbergen <feikesteenbergen(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15198: nextval() accepts tables/indexes when adding a default to a column
Date: 2018-05-18 01:12:11
Message-ID: 20180518011211.GA2437@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, May 17, 2018 at 12:36:31PM -0400, Alvaro Herrera wrote:
> [1] That syntax currently gets this funny error:
>
> alvherre=# create table ff (a int default seq.nextval);
> ERROR: missing FROM-clause entry for table "seq"

Which may be a parser problem as well seeing how CONSTR_DEFAULT gets
created using an expression?
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2018-05-18 01:41:01 Re: Abnormal JSON query performance
Previous Message David G. Johnston 2018-05-17 20:15:33 Re: BUG #15205: ERROR: table row type and query-specified row type do not match