| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Sergei Kornilov <sk(at)zsrv(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
| Subject: | Re: [HACKERS] generated columns |
| Date: | 2019-04-02 12:43:56 |
| Message-ID: | c743c3c6-93a3-0b23-20af-f0c15867f1d9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-04-01 10:52, Peter Eisentraut wrote:
> On 2019-03-31 05:49, Erik Rijkers wrote:
>> 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?
>
> I'll look into it.
I've been trying to create a test case for file_fdw for this, but I'm
not getting your result. Can you send a complete test case?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ibrar Ahmed | 2019-04-02 13:11:51 | Re: [PROPOSAL] Temporal query processing with range types |
| Previous Message | Amit Langote | 2019-04-02 12:26:26 | Re: Ordered Partitioned Table Scans |