Date: Sun, 20 Nov 2022 21:00:11 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Alexander Pyhalov <a.pyhalov@postgrespro.ru>
Cc: pgsql-hackers@lists.postgresql.org,
	Masahiko Sawada <sawada.mshk@gmail.com>,
	Michael Paquier <michael@paquier.xyz>,
	=?utf-8?B?5p2O5p2wKOaFjui/vSk=?= <adger.lj@alibaba-inc.com>,
	=?utf-8?B?5pu+5paH5peMKOS5ieS7jik=?= <wenjing.zwj@alibaba-inc.com>,
	Alvaro Herrera <alvherre@2ndquadrant.com>
Subject: Re: CREATE INDEX CONCURRENTLY on partitioned index
Message-ID: <20221121030011.GU11463@telsasoft.com>
References: <20201031063117.GF3080@telsasoft.com>
 <20201129202221.GA9477@telsasoft.com>
 <CAD21AoCHYE5=PU7kJGGUHZuYVrHTHqmpUxN+8-rLGYpdgPwJ9g@mail.gmail.com>
 <20210128143013.GC7450@telsasoft.com>
 <be8ff634-72c6-3fc7-9175-5a6b974af4a9@postgrespro.ru>
 <20210226182019.GU20769@telsasoft.com>
 <04657227cc37b6353cf0c72bedac70cc@postgrespro.ru>
 <20220628183309.GD28130@telsasoft.com>
 <bec008ae632d54b3d81af2ca86419732@postgrespro.ru>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="aPdhxNJGSeOG9wFI"
Content-Disposition: inline
In-Reply-To: <bec008ae632d54b3d81af2ca86419732@postgrespro.ru>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: 
 <https://www.postgresql.org/message-id/20221121030011.GU11463%40telsasoft.com>
Precedence: bulk


--aPdhxNJGSeOG9wFI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I finally found time to digest and integrate your changes into my local
branch.  This fixes the three issues you reported: FORCE_RELEASE, issue
with INVALID partitions issue (for which I adapted your patch into an
earlier patch in my series), and progress reporting.  And rebased.

-- 
Justin

--aPdhxNJGSeOG9wFI
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
 filename="0001-Allow-CREATE-INDEX-CONCURRENTLY-on-partitioned-table.patch"