Re: [HACKERS] logical decoding of two-phase transactions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] logical decoding of two-phase transactions
Date
Msg-id f351fc25-7b4d-3bf3-0398-d8a55bb3bd87@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] logical decoding of two-phase transactions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] logical decoding of two-phase transactions  (Nikhil Sontakke <nikhils@2ndquadrant.com>)
List pgsql-hackers
On 12/7/17 08:31, Peter Eisentraut wrote:
> On 12/4/17 10:15, Nikhil Sontakke wrote:
>> PFA, latest patch for this functionality.
> 
> This probably needs documentation updates for the logical decoding chapter.

You need the attached patch to be able to compile without warnings.

Also, the regression tests crash randomly for me at

frame #4: 0x000000010a6febdb
postgres`heap_prune_record_prunable(prstate=0x00007ffee5578990, xid=0)
at pruneheap.c:625
   622          * This should exactly match the PageSetPrunable macro.  We
can't store
   623          * directly into the page header yet, so we update working state.
   624          */
-> 625         Assert(TransactionIdIsNormal(xid));
   626         if (!TransactionIdIsValid(prstate->new_prune_xid) ||
   627             TransactionIdPrecedes(xid, prstate->new_prune_xid))
   628             prstate->new_prune_xid = xid;

Did you build with --enable-cassert?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Logical replication without a Primary Key
Next
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] CUBE seems a bit confused about ORDER BY