| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Chernow <ac(at)esilo(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: binary array and record recv |
| Date: | 2007-12-18 16:30:22 |
| Message-ID: | 535.1197995422@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Chernow <ac(at)esilo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Decibel! | 2007-12-18 16:41:20 | Re: VLDB Features |
| Previous Message | Andrew Chernow | 2007-12-18 16:09:09 | Re: binary array and record recv |