Re: Extended Query, flush or sync ?

From: Raimon Fernandez <coder(at)montx(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Extended Query, flush or sync ?
Date: 2009-12-18 23:40:06
Message-ID: 0251DAA7-FF5F-4F83-8F77-05A99EAB2432@montx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-interfaces


On 18/12/2009, at 22:55, Tom Lane wrote:

> Raimon Fernandez <coder(at)montx(dot)com> writes:
>> It's not clear for me if I have to issue a flush or sync after each process of an extended query.
>
> Basically, you send one of these at the points where you're going to
> wait for an answer back. Sync is different from Flush in that it also
> provides a resynchronization point after an error: when the backend hits
> an error while processing a given message, it ignores following messages
> up to the next Sync.

So I have to send on of these after sending a Parsing comand, a Bind comand, and Execute ?

It's normal that I don't receive nothing if I send a Flush instead of a Sync ?

regards and thanks,

raimon

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alex - 2009-12-18 23:48:07 Re: PL/Perl Performance Problems
Previous Message Tom Lane 2009-12-18 21:55:08 Re: Extended Query, flush or sync ?

Browse pgsql-interfaces by date

  From Date Subject
Next Message John DeSoi 2009-12-19 03:31:25 Re: Extended Query, flush or sync ?
Previous Message Tom Lane 2009-12-18 21:55:08 Re: Extended Query, flush or sync ?