Re: Two-phase commit case studies

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: Gavin Wahl <gwahl(at)fusionbox(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Two-phase commit case studies
Date: 2017-07-19 18:32:11
Message-ID: 87fuds46s4.fsf@jsievers.enova.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Gavin Wahl <gwahl(at)fusionbox(dot)com> writes:

> Hello,
>
> I've read the documentation for two-phase commit and it sounds interesting, but
> I'm having trouble thinking of how to actually put it into production. How are
> people using it? Do you use a XA transaction manager or something custom built?
> How dos the reconciliation work when a component crashes between PREPARE and
> COMMIT? Is anyone using it in the open-source world where transaction managers
> are unheard of?
>
> Looking forward to hearing about how two-phase commit has helped you.

I use it for holding an advisory lock the duration of any of our several
environment mangling frameworks.

We have fairly complex 1-touch provisioning, decom,
upgrade... rename/relocate/snapshot frameworks.

The lock is used to enforce cooperatively that no one else launches any
of those systems concurrently due to some interesting potential
conflicts.

>
> Thanks

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-07-19 18:42:07 Re: UPDATE column without FK fires other FK triggers constraint check
Previous Message Tom Lane 2017-07-19 18:30:54 Re: Support for \u0000?