From: Sergei Kornilov <sk@zsrv.org>
To: Riaan Stander <rstander@exa.co.za>
To: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: Prepared Transactions
Date: Mon, 11 Dec 2017 11:14:59 +0300
Message-ID: <96631512980099@web21g.yandex.ru> (raw)
In-Reply-To: <160430354e0.27df.e05fafc80f8daf1488764675043d44fb@exa.co.za>
References: <160430354e0.27df.e05fafc80f8daf1488764675043d44fb@exa.co.za>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sk@zsrv.org, rstander@exa.co.za, pgsql-performance@lists.postgresql.org
Subject: Re: Prepared Transactions
In-Reply-To: <96631512980099@web21g.yandex.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox