Message-ID: <ca74193b9b8c8906e4ba761de74e7c030ba50877.camel@cybertec.at>
Subject: Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Dmitry Koval <d.koval@postgrespro.ru>, PostgreSQL Hackers
	 <pgsql-hackers@lists.postgresql.org>
Date: Tue, 31 May 2022 13:02:27 +0200
In-Reply-To: <c73a1746-0cd0-6bdd-6b23-3ae0b7c0c582@postgrespro.ru>
References: <163714495450.16056.3566953095730878367@malur.postgresql.org>
	 <c73a1746-0cd0-6bdd-6b23-3ae0b7c0c582@postgrespro.ru>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/ca74193b9b8c8906e4ba761de74e7c030ba50877.camel%40cybertec.at>
Precedence: bulk

On Tue, 2022-05-31 at 12:32 +0300, Dmitry Koval wrote:
> There are not many commands in PostgreSQL for working with partitioned 
> tables. This is an obstacle to their widespread use.
> Adding SPLIT PARTITION/MERGE PARTITIONS operations can make easier to 
> use partitioned tables in PostgreSQL.
> (This is especially important when migrating projects from ORACLE DBMS.)
> 
> SPLIT PARTITION/MERGE PARTITIONS commands are supported for range 
> partitioning (BY RANGE) and for list partitioning (BY LIST).
> For hash partitioning (BY HASH) these operations are not supported.

+1 on the general idea.

At least, it will makes these operations simpler, but probably also less
invasive (no need to detach the affected partitions).


I didn't read the patch, but what lock level does that place on the
partitioned table?  Anything more than ACCESS SHARE?


Yours,
Laurenz Albe