Re: a misbehavior of partition row movement (?)

> @@ -3398,7 +3432,7 @@ typedef SetConstraintStateData *SetConstraintState;
>   */
>  typedef uint32 TriggerFlags;
>  
> -#define AFTER_TRIGGER_OFFSET            0x0FFFFFFF    /* must be low-order bits */
> +#define AFTER_TRIGGER_OFFSET            0x07FFFFFF    /* must be low-order bits */
>  #define AFTER_TRIGGER_DONE                0x10000000
>  #define AFTER_TRIGGER_IN_PROGRESS        0x20000000
>  /* bits describing the size and tuple sources of this event */
> @@ -3406,7 +3440,8 @@ typedef uint32 TriggerFlags;
>  #define AFTER_TRIGGER_FDW_FETCH            0x80000000
>  #define AFTER_TRIGGER_1CTID                0x40000000
>  #define AFTER_TRIGGER_2CTID                0xC0000000
> -#define AFTER_TRIGGER_TUP_BITS            0xC0000000
> +#define AFTER_TRIGGER_CP_UPDATE            0x08000000
> +#define AFTER_TRIGGER_TUP_BITS            0xC8000000

So this patch releases one bit from AFTER_TRIGGER_OFFSET and makes it
become AFTER_TRIGGER_CP_UPDATE.  As far as I can tell there is no harm
in doing so.

-- 
Álvaro Herrera           39°49'30"S 73°17'W  —  https://www.EnterpriseDB.com/