Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed

Amit Langote <langote_amit_f8@lab.ntt.co.jp>

View thread View on postgr.es

From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>

To: Tom Lane <tgl@sss.pgh.pa.us>, r.zharkov@postgrespro.ru

Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, pgsql-bugs@lists.postgresql.org

Date: 2019-04-08T08:18:48Z

Lists: pgsql-bugs

Attachments

pg11-10-bug-15677-fix-with-test_v2.patch (text/plain) patch v2

On 2019/04/08 16:21, Amit Langote wrote:
> Now that Andres has taken care of the other issues [1], maybe this one's
> good to go?  The isolation test part needed to be rebased over Andres'
> commit, which I've done in the attached updated patch.

The patch I attached in the previous email doesn't apply as-is to
back-branches due to rebasing.  I've attached another patch here, which
applies to both PG 11 and 10 branches.

Thanks,
Amit

Commits

Fix GetNewTransactionId()'s interaction with xidVacLimit.
- f7feb020c3d8 12.0 landed
Fix example in comment.
- 16954e22e2a8 12.0 cited
Fix EvalPlanQualStart to handle partitioned result rels correctly.
- 1b5bbe4bcc91 10.8 landed
- b291488da513 11.3 landed
- a8cb8f124679 12.0 landed
Fix a number of issues around modifying a previously updated row.
- 41f5e04aec6c 12.0 landed
Use FullTransactionId for the transaction stack.
- ad308058cc86 12.0 cited
Add basic infrastructure for 64 bit transaction IDs.
- 2fc7af5e9660 12.0 cited
tableam: Add tuple_{insert, delete, update, lock} and use.
- 5db6df0c0117 12.0 cited
Throw error if expiring tuple is again updated or deleted.
- 6868ed7491b7 9.3.0 cited