From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andreas Joseph Krogh <andreas@visena.com>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: ERROR: attribute number 6 exceeds number of columns 5
In-reply-to: <VisenaEmail.200.231b0a41523275d0.16ea7f800c7@tc7-visena>
References: <VisenaEmail.200.231b0a41523275d0.16ea7f800c7@tc7-visena>
Comments: In-reply-to Andreas Joseph Krogh <andreas@visena.com>
	message dated "Tue, 26 Nov 2019 15:04:51 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6351.1574783351.1@sss.pgh.pa.us>
Date: Tue, 26 Nov 2019 10:49:11 -0500
Message-ID: <6352.1574783351@sss.pgh.pa.us>
Precedence: bulk

Andreas Joseph Krogh <andreas@visena.com> writes:
> Run the attached script and you'll get: 

> psql -f error.sql -d test 
> psql:error.sql:37: ERROR: attribute number 6 exceeds number of columns 5

Hmm, interesting.  IMO, that *should* have thrown an error, but of
course not that one.  The ADD COLUMN operations are all processed
in parallel, so it's not okay for one of them to have a GENERATED
expression that refers to another one of the new columns.  But you
should have gotten a "no such column" type of error, not a run-time
cross-check failure.

			regards, tom lane