| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Better error message for select_common_type() |
| Date: | 2008-03-18 18:45:17 |
| Message-ID: | 200803181945.17916.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Dienstag, 18. März 2008 schrieb Tom Lane:
> Or we could apply Peter's patch more or less as-is, but I don't like
> that. I don't think it solves the stated problem: if you know that CASE
> branches 3 and 5 don't match, that still doesn't help you in a monster
> query with lots of CASEs. I think we can and must do better.
Yeah, that and the other reason I sort of gave up on this approach is that it
is nearly impossible to find some good terminology that works for all callers
of select_common_type() (VALUES, UNION, JOIN, IN, CASE, ARRAY, COALESCE,
GREATEST, according to my notes). A pointer into the statement would
certainly be much nicer.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Denis Vnukov @ Nabble | 2008-03-18 19:17:39 | Problems with compilation of user-defined C functions for PostgreSQL 8.3.0 |
| Previous Message | Bruce Momjian | 2008-03-18 18:41:24 | Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) |