Re: BUG #16395: error when selecting generated column in a foreign table - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #16395: error when selecting generated column in a foreign table
Date
Msg-id CAL2+1fk30asz7ok5tW_9-rA1=8yTy5m5YfOdQtXiEvJE+ybGZg@mail.gmail.com
Whole thread Raw
In response to BUG #16395: error when selecting generated column in a foreign table  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Here is a test case that shows that it works:

create extension postgres_fdw;

create server fs_postgres foreign data wrapper postgres_fdw options
(dbname 'postgres');

create user mapping for current_user server fs_postgres;

CREATE TABLE public.test (
    id integer PRIMARY KEY,
    field1 integer NOT NULL,
    field2 character varying,
    field_calc integer
);

CREATE FOREIGN TABLE public.test_ft (
    id integer,
    field1 integer,
    field2 character varying,
    field_calc integer generated always as (field1 * 2) stored
)
SERVER fs_postgres OPTIONS(table_name 'test');

insert into test_ft (id, field1, field2) values (1, 2, 'one');

select * from test_ft;
 id | field1 | field2 | field_calc
----+--------+--------+------------
  1 |      2 | one    |          4

select * from test;
 id | field1 | field2 | field_calc
----+--------+--------+------------
  1 |      2 | one    |          4

In your case, were you adding columns to existing tables? Depending on
the order of actions, it might not work the way one might think.

Can you reproduce your problem from a blank database?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Equality of columns isn't taken in account when performing partitionpruning
Next
From: David Rowley
Date:
Subject: Re: Equality of columns isn't taken in account when performingpartition pruning