On 2019-01-16 22:40, Erik Rijkers wrote:
>
> If you add a generated column to a file_fdw foreign table, it works OK
> wih VIRTUAL (the default) but with STORED it adds an empty column,
> silently. I would say it would make more sense to get an error.
VIRTUAL is gone, but that other issue is still there: STORED in a
file_fdw foreign table still silently creates the column which then
turns out to be useless on SELECT, with an error like:
"ERROR: column some_column_name is a generated column
DETAIL: Generated columns cannot be used in COPY."
Maybe it'd be possible to get an error earlier, i.e., while trying to
create such a useless column?
thanks,
Erik Rijkers