Re: binary array and record recv - Mailing list pgsql-hackers

From Tom Lane
Subject Re: binary array and record recv
Date
Msg-id 535.1197995422@sss.pgh.pa.us
Whole thread Raw
In response to Re: binary array and record recv  (Andrew Chernow <ac@esilo.com>)
Responses Re: binary array and record recv  ("Merlin Moncure" <mmoncure@gmail.com>)
Re: binary array and record recv  (Andrew Chernow <ac@esilo.com>)
Re: binary array and record recv  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Andrew Chernow <ac@esilo.com> writes:
> When dealing with binary, the Oid the client sends may match what the 
> server thinks but the data is wrong (client sent binary formatted data 
> of the wrong type).  Thus, the only real check we saw was on the data 
> length (which is rolling the dice).

Yes, the available checks to detect client-vs-server datatype mismatch
are very weak, but that hardly comes across as a good argument for
removing one of the ones we have.

> How is the client supposed to send back composite types without having a 
> meaningful way to get the Oids from the server?

On what grounds do you claim that it can't get the type Oids from the
server?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Chernow
Date:
Subject: Re: binary array and record recv
Next
From: Tom Lane
Date:
Subject: Re: ecxt_scantuple has wrong TupleDesc