Re: Better error message for select_common_type()

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Better error message for select_common_type()
Date: 2008-03-18 00:31:43
Message-ID: 87ve3kan4g.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> 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.

Do we have something more helpful than "branches 3 and 5"? Perhaps printing
the actual transformed expressions?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-03-18 00:43:36 Re: [something I can't read]
Previous Message 张 海 泉 2008-03-18 00:26:50 业务合办 ！