Re: Store FullTransactionId in TwoPhaseFileHeader/GlobalTransactionData

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Store FullTransactionId in TwoPhaseFileHeader/GlobalTransactionData
Date: 2019-08-01 12:05:55
Message-ID: CA+hUKG+2gcNGZ1CTjU02XjgRwZ7RKnbnFiS1Hs3EBg84T6u7UA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Vignesh,

On Thu, Aug 1, 2019 at 9:32 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> In the undo system, we use full-transaction-id for transactions. For
> rollback of prepared transactions, we were planning to use
> FullTransactionId by combining TransactionId and epoch, but as
> suggested by multiple people in that email chain [1][2], the better
> idea is to store Full-transactionid in TwoPhaseFileHeader

+1

> Backward compatibility need not be handled for this scnario as upgrade
> does not support having open prepared transactions.

+1

> There is also one more comment which is yet to be concluded. The
> comment discusses about changing subxids which are of TransactionId
> type to FullTransactionId type being written in two phase transaction
> file. We could not conclude this as the data is similarly stored in
> TransactionStateData.

No comment on that question or the patch yet but could you please add
this to the next Commitfest so that cfbot starts testing it?

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2019-08-01 12:14:03 Re: How to retain lesser paths at add_path()?
Previous Message legrand legrand 2019-08-01 12:01:17 Re: How to install login_hook in Postgres 10.5