Date: Mon, 17 Jan 2022 18:22:19 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>,
	Ibrar Ahmed <ibrar.ahmad@gmail.com>,
	Arne Roland <A.Roland@index.de>,
	"David G. Johnston" <david.g.johnston@gmail.com>,
	Masahiko Sawada <sawada.mshk@gmail.com>,
	Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	Rahila Syed <rahilasyed90@gmail.com>,
	Tomas Vondra <tomas.vondra@2ndquadrant.com>
Subject: Re: a misbehavior of partition row movement (?)
Message-ID: <202201172122.2bikr3kpfm27@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CA+HiwqH2gWBDUotwtnY7qnp+K5j0J4tzUDycqcePA7Yy1s4MbQ@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202201172122.2bikr3kpfm27%40alvherre.pgsql>
Precedence: bulk


> @@ -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/