| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Thiede, Christoph" <Christoph(dot)Thiede(at)student(dot)hpi(dot)uni-potsdam(dot)de> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Stored columns: Unexpected varattno in expression to be mapped |
| Date: | 2020-07-16 16:10:35 |
| Message-ID: | 3360959.1594915835@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Thiede, Christoph" <Christoph(dot)Thiede(at)student(dot)hpi(dot)uni-potsdam(dot)de> writes:
> as a Postgres user for about half a year, I think I found a bug in psql (PostgreSQL) 12.2 (Debian 12.2-2.pgdg100+1).
> Steps to reproduce:
> postgres=# create table mytable (foo text generated always as (bar) stored, bar text);
> CREATE TABLE
> postgres=# create temporary table mytemp1 (like mytable);
> CREATE TABLE
> postgres=# create temporary table mytemp2 (like mytable including all);
> ERROR: unexpected varattno 2 in expression to be mapped
Thanks for the report! Trying this locally, it seems to work in
either HEAD or v12 branch tip, so I think we fixed the bug already.
I recall some recent work around this area, so that conclusion
is not surprising. What I don't recall is whether those fixes
were before or after 12.3. You might find that updating to 12.3
fixes it; if not, it should be fixed in next month's 12.4 release.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-07-17 00:50:50 | Re: Stored columns: Unexpected varattno in expression to be mapped |
| Previous Message | David G. Johnston | 2020-07-16 16:05:31 | Re: Stored columns: Unexpected varattno in expression to be mapped |