Re: Postgre Protocol - Mailing list pgsql-novice

From Greg
Subject Re: Postgre Protocol
Date
Msg-id 764101.17661.qm@web24305.mail.ird.yahoo.com
Whole thread Raw
In response to Re: Postgre Protocol  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postgre Protocol  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-novice
Hi Tom, thanks for the quick reply. I've looked at the break points and you are right there are 7 more bytes with data send with AuthenticationOk message, so I think thats what I need to look at :) (Im sure this is just a confirmation that everything is ok).

May I ask, sequence of bytes after the AuthenticationOk messages is: 0080003; Is this sequence represent BackendKeyData or values for Authentication*** status codes, or Im completely worng and it is realy nothing but confirmation for a frontend how the database applied options passed with start-up packet?

Thanks!
Greg.




--- On Mon, 28/6/10, Tom Lane <tgl@sss.pgh.pa.us> wrote:

From: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: [NOVICE] Postgre Protocol
To: "Greg" <grigorey@yahoo.co.uk>
Cc: pgsql-novice@postgresql.org
Date: Monday, 28 June, 2010, 19:08

Greg <grigorey@yahoo.co.uk> writes:
> So question is after I recive AuthenticationOk, do I need to wait for
> ReadyForQuery message from the database

Yes.  You should have gotten it --- the backend is designed to coalesce
those messages into a single network packet, so as to avoid extra
network traffic.  I wonder whether your code is failing to notice
additional logical messages arriving in the same bufferload.

            regards, tom lane

pgsql-novice by date:

Previous
From: raghu ram
Date:
Subject: Prepared statement issue in Pgpool-II
Next
From: Tom Lane
Date:
Subject: Re: Postgre Protocol