Andrew Dunstan wrote:
> I have just discovered that the recently implemented pipe chunking
> protocol is broken on Windows. This is because the pipes are operating
> in text mode and doing LF->CR-LF translation, so the number of bytes
> received is not the number transmitted and set in the protocol header.
> I have not yet succeeded in turning this behaviour off (_setmode()
> didn't seem to affect it). If we can't find a way to turn it off, the
> only solution short of abandoning its use on Windows that I can think of
> is to translate LF on input to something unlikely like 0x1C and then
> translate it back when we read it from the pipe.

At what point does it actually do the translation? Meaning what
system/library call has it?

Are we using the pipes from src/port/pipe.c? It does sound a bit weird
that they'd do that, since it's basically just emulating stuff over
standard tcp sockets, but perhaps something is broken in that code?

Sorry, haven't really checked up on the chunk code yet, so I don't know
offhand where to look.


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to