Re: Old protocol fastpath calls borked? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Old protocol fastpath calls borked?
Date
Msg-id 20190124221111.zwuu7epi3bgrnoky@alap3.anarazel.de
Whole thread Raw
In response to Re: Old protocol fastpath calls borked?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Old protocol fastpath calls borked?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2019-01-24 17:04:32 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > In parse_fcall_arguments_20():
> > we appear to constantly setting argnull to true for all arguments?
> 
> Uh, it looks to me like it does so only if the frontend sends a -1
> length field, which is the protocol's convention for indicating a
> null.

Ah, brainfade.  Probably triggered by the fact that I forgot that we call
input functions even on NULL (which never quite made sense to me).

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal - plpgsql unique statement id
Next
From: Tom Lane
Date:
Subject: Re: Old protocol fastpath calls borked?