Re: Problem trying to implement version 3.0 of the PostgreSQL protocol - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Problem trying to implement version 3.0 of the PostgreSQL protocol
Date
Msg-id 27324.1054761416@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problem trying to implement version 3.0 of the PostgreSQL protocol  (Carlos Guzman Alvarez <carlosga@telefonica.net>)
List pgsql-hackers
Carlos Guzman Alvarez <carlosga@telefonica.net> writes:
> You are right thanks very much, but now i have another problem, i don't 
> get response from the postgresql server, hummm this is what i'm sending 
> for test:

Your Parse message looks fine, but the server will not actually send its
ParseComplete response until you send a Sync or Flush message.  The idea
is that Parse is usually going to be part of a series of operations, and
you don't want a separate network packet coming back for each operation
in the series.  When you do want to see the results of an operation
before you issue the next one, you can issue either Flush (just forces
out the pending messages) or Sync (which does all the stuff that was
formerly done at the end of a Query message).

Error messages do get flushed out immediately, which is why you were
able to see the response in the other case.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Aggregates containing outer references don't work per spec
Next
From: Carlos Guzman Alvarez
Date:
Subject: Re: Problem trying to implement version 3.0 of the PostgreSQL protocol