| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Supporting $n parameters in new syntax |
| Date: | 2021-05-18 23:46:15 |
| Message-ID: | CA+renyVBgdJfCtH3V2gXHqMxt_hZYHCE8GFGGD0N0GFKejqabQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 18, 2021 at 3:00 PM Paul A Jungwirth
<pj(at)illuminatedcomputing(dot)com> wrote:
>
> I suspect I'm missing something in the
> analyze/rewriting phase, because I get this error:
>
> ERROR: no value found for parameter 1
> . . .
>
> I was hoping that transformExpr would do everything I need re
> identifying parameters, but maybe there is something else in a later
> phase?
Never mind, I think I figured it out. The problem was that I was
calling ExecEvalExpr with CreateStandaloneExprContext(), and I should
have been using the context from the query.
Thanks!
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-05-19 00:44:48 | Re: pg_dumpall misses --no-toast-compression |
| Previous Message | Tom Lane | 2021-05-18 23:45:04 | Re: pgbench test failing on 14beta1 on Debian/i386 |