| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] generated columns |
| Date: | 2018-01-26 17:46:56 |
| Message-ID: | CA+TgmoaT671B6my-S+1W6hGYr9SnxQg1Jpo4yDceqmt3YQ-o4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 25, 2018 at 10:26 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> Does the SQL spec mention the matter? How do other systems
>> handle such cases?
>
> In Oracle you get the same overflow error.
That seems awful. If a user says "SELECT * FROM tab" and it fails,
how are they supposed to recover, or even understand what the problem
is? I think we should really try to at least generate an errcontext
here:
ERROR: integer out of range
CONTEXT: while generating virtual column "b"
And maybe a hint, too, like "try excluding this column".
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-01-26 18:01:08 | Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation) |
| Previous Message | Robert Haas | 2018-01-26 17:39:35 | Re: Removing WITH clause support in CREATE FUNCTION, for isCachable and isStrict |