> It's part of the protocol, actually (yes, two NUL bytes -- first one
> signals the end of the previous string, the second one signals the end
> of the packet).
The end of the packet can be obtained by packet length
----- Original Message -----
From: "Alvaro Herrera" <alvherre@commandprompt.com>
To: <Eugen.Konkov@aldec.com>
Cc: <pgsql-bugs@postgresql.org>
Sent: Wednesday, April 16, 2008 5:27 PM
Subject: Re: [BUGS] BUG: Protocol 3.0 ErrorResponse: Last 'null'
characterseems odd
> Eugen.Konkov@aldec.com wrote:
>> 53 46 41 54 41 4C 00 43 30 38 50 30 31 00 4D 69 SFATAL.C08P01.Mi
>> 6E 76 61 6C 69 64 20 73 74 61 72 74 75 70 20 70 nvalid.startup.p
>> 61 63 6B 65 74 20 6C 61 79 6F 75 74 3A 20 65 78 acket.layout:.ex
>> 70 65 63 74 65 64 20 74 65 72 6D 69 6E 61 74 6F pected.terminato
>> 72 20 61 73 20 6C 61 73 74 20 62 79 74 65 00 46 r.as.last.byte.F
>> 2E 5C 73 72 63 5C 62 61 63 6B 65 6E 64 5C 70 6F .\src\backend\po
>> 73 74 6D 61 73 74 65 72 5C 70 6F 73 74 6D 61 73 stmaster\postmas
>> 74 65 72 2E 63 00 4C 31 35 35 37 00 52 50 72 6F ter.c.L1557.RPro
>> 63 65 73 73 53 74 61 72 74 75 70 50 61 63 6B 65 cessStartupPacke
>> 74 00 00 t..
>>
>> Last 'null' character seems odd
>
> It's part of the protocol, actually (yes, two NUL bytes -- first one
> signals the end of the previous string, the second one signals the end
> of the packet).
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> The PostgreSQL Company - Command Prompt, Inc.