From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: MERGE and parsing with prepared statements |
Date: | 2022-07-15 19:53:59 |
Message-ID: | CAKFQuwZPuwyg=29ssWrO7oeJM4UFpwm3CSmbPMUDc34Y5Uso_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 15, 2022 at 12:40 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> On Fri, Jul 15, 2022 at 12:17:51PM -0700, David G. Johnston wrote:
> > On Fri, Jul 15, 2022 at 11:40 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> wrote:
> > > On 2022-Jul-15, Justin Pryzby wrote:
> > >
> > > > It seems a bit odd that it's impossible to use merge with prepared
> statements
> > > > without specifically casting the source types (which I did now to
> continue my
> > > > experiment).
> > >
> > > I have no comments on this. Maybe it can be improved, but I don't know
> > > how.
> >
> > Not tested, but the example prepare command fails to make use of the
> > optional data types specification. Using that should remove the need to
> > cast the parameter placeholder within the query itself.
>
> What optional data type specification ?
>
The one documented here:
https://www.postgresql.org/docs/current/sql-prepare.html
PREPARE name [ ( data_type [, ...] ) ] AS statement
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-07-15 19:59:34 | Re: MERGE and parsing with prepared statements |
Previous Message | Tomas Vondra | 2022-07-15 19:46:51 | Re: POC: GROUP BY optimization |