This is a little rudimentary, though I like it in its simplicity and to keep in mind xxd, which is an interesting command line tool (I don't have to do a lot of work on hex, though). Once you make the changes (in the hex part), you can go back to text with -r command on xxd, so : enters command-line mode, % matches whole file as a range, ! filters that range through an external command, xxd is that external shell command As far as it's concerned, it's not correlated to any query.You can use the xxd command to transform a file in Vim to hex representation, doing On the postgres server side, I don't think you can get more information beyond the mentioned error, because the backend gives up on the message at the first byte. Wireshark knows about the PGSQL protocol. If the traffic is not encrypted, a packet inspection tool like Wireshark might help to look into these packets. The value 74 from the error message would be 'J', but according to the doc this message type is not used for anything in any version of the protocol, so the client or middleware sending it must be misbehaving. For example, if a client issues a "Bind", the first byte is the ASCII code for ' B', or 66. The type of the message is given by the first byte. I can't find any documentation on frontend messageĪnd a more general description of the protocol is at: I'm getting this error and I have no idea where it's coming from or
0 kommentar(er)
