| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: logical decoding of two-phase transactions |
| Date: | 2017-02-02 19:33:21 |
| Message-ID: | CA+TgmoZN5ziYFaOCnXjvAbGAODo5oNVSNadHUcUevHWk9cf3Yw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 1, 2017 at 2:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Also, including the GID in the WAL for each COMMIT/ABORT PREPARED
>> doesn't seem inordinately expensive to me.
>
> I'm confused ... isn't it there already? If not, how do we handle
> reconstructing 2PC state from WAL at all?
By XID. See xl_xact_twophase, which gets included in xl_xact_commit
or xl_xact_abort. The GID has got to be there in the XL_XACT_PREPARE
record, but not when actually committing/rolling back.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-02-02 19:34:31 | Re: logical decoding of two-phase transactions |
| Previous Message | Jesper Pedersen | 2017-02-02 19:28:50 | Re: pageinspect: Hash index support |