Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1eOJEy-0004fs-H6
	for pgsql-performance@arkaria.postgresql.org; Mon, 11 Dec 2017 08:15:08 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1eOJEx-00030F-LA
	for pgsql-performance@arkaria.postgresql.org; Mon, 11 Dec 2017 08:15:07 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <sk@zsrv.org>)
	id 1eOJEx-000303-CV
	for pgsql-performance@lists.postgresql.org; Mon, 11 Dec 2017 08:15:07 +0000
Received: from forward3p.cmail.yandex.net ([77.88.31.18])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <sk@zsrv.org>)
	id 1eOJEu-0005zr-Ak
	for pgsql-performance@lists.postgresql.org; Mon, 11 Dec 2017 08:15:06 +0000
Received: from mxback4o.mail.yandex.net (mxback4o.mail.yandex.net
 [IPv6:2a02:6b8:0:1a2d::1e])
	by forward3p.cmail.yandex.net (Yandex) with ESMTP id F1A8020D4B;
	Mon, 11 Dec 2017 11:15:01 +0300 (MSK)
Received: from web21g.yandex.ru (web21g.yandex.ru [2a02:6b8:0:1402::31])
	by mxback4o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id
 D7USX8ZtiJ-ExAWEMfT;
	Mon, 11 Dec 2017 11:15:01 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail;
 t=1512980101;
	bh=B1ysGCrQgzMSgml6mYRxrvCDgG2HYnhLvBWcgREOyuQ=;
	h=From:To:In-Reply-To:References:Subject:Message-Id:Date;
	b=g+VmNOItCEsV3nEEA2WzODsw6k29Ngd7t1jhR6331Q6IvAUs/xVt0P3fIY6rvL6wb
	 14P70WGH9YJPNEC0wyAiiWHqIPE8a1X9Ak0VMlW1/7sSuii1Y9SEblU8q2l0FOATdS
	 x3QleVqiCnkLaNx56LVXY4XieIDDjiy4l3dsLx2g=
Authentication-Results: mxback4o.mail.yandex.net; dkim=pass header.i=@zsrv.org
Received: by web21g.yandex.ru with HTTP;
	Mon, 11 Dec 2017 11:14:59 +0300
From: Sergei Kornilov <sk@zsrv.org>
To: Riaan Stander <rstander@exa.co.za>,
	"pgsql-performance@lists.postgresql.org"
 <pgsql-performance@lists.postgresql.org>
In-Reply-To: <160430354e0.27df.e05fafc80f8daf1488764675043d44fb@exa.co.za>
References: <160430354e0.27df.e05fafc80f8daf1488764675043d44fb@exa.co.za>
Subject: Re: Prepared Transactions
MIME-Version: 1.0
Message-Id: <96631512980099@web21g.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Mon, 11 Dec 2017 11:14:59 +0300
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

Hello!

You need prepared transactions only if you need two-phase commit to provide distributed atomic transaction on multiple different databases.
If you not need distributed transactions - you not needed prepared transactions at all.
But if you need distributed transactions - here is no more choice regardless performance questions.

As say in documentation https://www.postgresql.org/docs/current/static/sql-prepare-transaction.html
> Unless you're writing a transaction manager, you probably shouldn't be using PREPARE TRANSACTION.

Regards, Sergei