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

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: Жарков Роман <r.zharkov@postgrespro.ru>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

Date: 2019-04-12T05:39:21Z

Lists: pgsql-bugs

On Fri, Apr 12, 2019 at 5:19 PM Michael Paquier <michael@paquier.xyz> wrote:
> On Fri, Apr 12, 2019 at 05:04:53PM +1200, Thomas Munro wrote:
> > On Fri, Apr 12, 2019 at 2:44 PM <r.zharkov@postgrespro.ru> wrote:
> >> My test finished successfully. Everything is OK.
> >
> > Pushed.  Thanks for the report and testing!
>
> Could you mark this item in [1] as fixed please?

Oops, done (moved to the fixed items list).

-- 
Thomas Munro
https://enterprisedb.com

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