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

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: r.zharkov@postgrespro.ru

Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org

Date: 2019-04-11T03:47:30Z

Lists: pgsql-bugs

On Thu, Apr 11, 2019 at 10:29:03AM +0700, r.zharkov@postgrespro.ru wrote:
> The error does not reproduce on commit 2fc7af5 on both servers.

Okay.  As nothing seems to remain here, I have marked this open item
as fixed.
--
Michael

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