Received: from localhost (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id A4EAF632C59
	for <pgsql-general-postgresql.org@mail.postgresql.org>;
	Fri, 18 Dec 2009 17:55:42 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024)
	with ESMTP id 59584-06
	for <pgsql-general-postgresql.org@mail.postgresql.org>;
	Fri, 18 Dec 2009 21:55:26 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 85E366329FC
	for <pgsql-general@postgresql.org>;
	Fri, 18 Dec 2009 17:55:19 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id nBILt8O5012276;
	Fri, 18 Dec 2009 16:55:08 -0500 (EST)
To: Raimon Fernandez <coder@montx.com>
cc: pgsql-general@postgresql.org
Subject: Re: Extended Query, flush or sync ? 
In-reply-to: <AC4D2602-8300-41E5-BF48-67C39CD95BBF@montx.com> 
References: <92781008-8A70-42CE-A49B-6EE67103FACB@montx.com>
	<FC6CBC8C-A398-4835-B3A3-C16C6F4F62D9@pgedit.com>
	<E084987E-A212-4B70-8CFF-D83AA00629C5@montx.com>
	<C670629A-1E54-4F80-9497-6CCAC1A8BDC0@montx.com>
	<20091026231516.GN8812@alvh.no-ip.org>
	<4AE62E21.7040600@hogranch.com>
	<66F15D69-75E5-4D8E-84F8-2F21E09BBA98@pgedit.com>
	<9A9F2678-36B9-42A2-91B2-69076065E8EB@montx.com>
	<20091027134158.GB4876@alvh.no-ip.org>
	<4AB34FE9-CC23-48BE-B905-6478304E0E5B@montx.com>
	<20091027140657.GF4876@alvh.no-ip.org>
	<B7382F17-63B5-49D0-8E39-0F46F9243C95@montx.com>
	<B1EA5872-6E57-46A8-BF35-3192707A5C0F@montx.com>
	<A8F7FAA5-A817-4CCE-BA06-BF28B5534AC7@montx.com>
	<4B057205.6000203@gmail.com>
	<A86C9188-4DAC-4EC4-86BD-0B483287BC71@montx.com>
	<322BBEA5-A328-4197-971E-95359D8FD7F3@montx.com>
	<4B05A8D4.7020500@gmail.com>
	<6A231EA8-5255-47F3-BECB-9BFBD700044C@montx.com>
	<20879F35-6940-4272-988E-703E610C6212@montx.com>
	<57FE8BF9-5E03-4F5A-9BBA-A06118CC2E3B@pgedit.com>
	<0AADF4A5-E795-4F2D-AA2B-A4E1A4B!
	D 9D93@montx.com> <AC4D2602-8300-41E5-BF48-67C39CD95BBF@montx.com>
Comments: In-reply-to Raimon Fernandez <coder@montx.com>
	message dated "Fri, 18 Dec 2009 22:44:10 +0100"
Date: Fri, 18 Dec 2009 16:55:08 -0500
Message-ID: <12275.1261173308@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.545 tagged_above=-10 required=5 tests=AWL=0.054,
	BAYES_00=-2.599
X-Spam-Level: 
X-Archive-Number: 200912/871
X-Sequence-Number: 157091

Raimon Fernandez <coder@montx.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.

			regards, tom lane