Re: [HACKERS] Prepared statements assume text type in PG10 - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] Prepared statements assume text type in PG10
Date
Msg-id CAH2-Wz=QZr4cpw1VzaiUa2yovLMBkwaEf-Kj-RduZHdosndKWw@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Prepared statements assume text type in PG10  (Jack Christensen <jack@jackchristensen.com>)
Responses Re: [HACKERS] Prepared statements assume text type in PG10
List pgsql-hackers
On Sat, Oct 7, 2017 at 2:56 PM, Jack Christensen
<jack@jackchristensen.com> wrote:
> The test suite for the Go PostgreSQL driver pgx
> (https://github.com/jackc/pgx) found an unexpected behavior change in PG10.
> Previously, it was impossible to prepare a statement with a unknown or
> ambiguous parameter type.
>
> Pre-version 10:
>
> jack=# prepare ps as select $1;
> ERROR:  could not determine data type of parameter $1
>
> But on PG10 the type defaults to text:
>
> jack=# prepare ps as select $1;
> PREPARE
> Time: 0.183 ms
> jack=# execute ps('Hello, there');
>    ?column?
> --------------
>  Hello, there
> (1 row)
>
> Time: 0.437 ms
>
> I looked through the git log and couldn't find any commits referencing this.
> Is this an intended behavior change?

I suspect commit d8d32d9 is involved here, though I haven't verified that.

-- 
Peter Geoghegan


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updatedtuple
Next
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] Prepared statements assume text type in PG10