From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | rep(dot)dot(dot)nop(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15109: Unhelpful error message on type mismatch |
Date: | 2018-03-13 22:36:36 |
Message-ID: | 7087.1520980596@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tue, Mar 13, 2018 at 1:46 PM, PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>> psql:xxx.sql:19: ERROR: type of parameter 4 (bigint) does not match that
>> when preparing the plan (text)
>> CONTEXT: PL/pgSQL function xxx(boolean) line 12 at RETURN
> In short - this isn't a bug report so this isn't the right list for the
> discussion (that would be -general), and while the frustration is real the
> proposed alternatives do not seem realistic.
Ideally, of course, we'd like to not see this error at all, at least not
in the context of plpgsql --- it should auto-replan affected statements
when a record column changes type. That's been on the to-do list for a
long time, though, and hasn't gotten done. When it does get done it's
unlikely to be something we'd risk back-patching.
So you could call this a bug if you want, but when it does get fixed
it'll be treated as a new feature instead.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2018-03-14 00:38:45 | Re: BUG #15104: Double free in the main function in ecpg.c |
Previous Message | David G. Johnston | 2018-03-13 21:17:29 | Re: BUG #15109: Unhelpful error message on type mismatch |