server side: writeInt32( length($message)+4 ); writeString( $message );
client side: $length= readInt32(); readString( $length -4 )
that's just odd, needing to add the number of bytes the length field occupies
This is simpler:
server side: writeInt32( length($message)); writeString( $message );
The following bug has been logged online:
Bug reference: 4109
Logged by: Fujii Masao
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: All
Description:Typo in documentation
Details:
I found the typo in
http://www.postgresql.org/docs/8.3/stat
[EMAIL PROTECTED] 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
>
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
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" <[EMAIL PROTECTED]>
To: <[EMAI
Fujii Masao wrote:
The following bug has been logged online:
Bug reference: 4109
Logged by: Fujii Masao
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: All
Description:Typo in documentation
Details:
I found the typo in
http://www.postgre
<[EMAIL PROTECTED]> writes:
>> 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
It's designed that way intentionally to aid in
<[EMAIL PROTECTED]> writes:
> Will you plan to correct that in Protocol 3.1?
No.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
[EMAIL PROTECTED] wrote:
> server side: writeInt32( length($message)+4 ); writeString( $message );
> client side: $length= readInt32(); readString( $length -4 )
>
> that's just odd, needing to add the number of bytes the length field occupies
>
> This is simpler:
> server side: writeInt32( leng
Heikki Linnakangas wrote:
I found the typo in
http://www.postgresql.org/docs/8.3/static/datatype-enum.html .
The length of an enum value's textual label is limited by the NAMEDATALEN
setting compiled into PostgreSQL; in standard builds this means at most 63
bytes.
Correct is that the NAMEDATA
10 matches
Mail list logo
