On Tue, Dec 5, 2017 at 11:06 PM, Vitaliy Garnashevich <
vgarnashev...@gmail.com> wrote:
This is very cool, thanks.
> I've tried to create a better test case:
> - Increase shared_buffers and effective_cache_size to fit whole database,
> including indexes.
> - Use random(), to avoid correlation b
Hi Riaan,
You benefit from greater fault tolerance performance. Recovering from
a crash/network outage is quicker/easier.
On the downside you might see a reduction in transactions per second.
It's worth benchmarking. To see if the impact to tps is acceptable to
live with.
Jeremy
On Mon, 2017-
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 ch
