Re: [PATCH] Automatic HASH and LIST partition creation

Couple of comments: 

1. The syntax used omits the { IMMEDIATE | DEFERRED} keywords suggested in 

the earlier discussions. I think it is intuitive to include IMMEDIATE with the current implementation

so that the syntax can be extended with a  DEFERRED clause in future for dynamic partitions.

  CREATE TABLE tbl_lst (i int) PARTITION BY LIST (i)
 CONFIGURATION (values in (1, 2), (3, 4) DEFAULT PARTITION tbl_default);

 

After some consideration, I decided that we don't actually need to introduce IMMEDIATE | DEFERRED keyword. For hash and list partitions it will always be immediate, as the number of partitions cannot change after we initially set it. For range partitions, on the contrary, it doesn't make much sense to make partitions immediately, because in many use-cases one bound will be open.

     2. One suggestion for generation of partition names is to append a unique id to

avoid conflicts.

Can you please give an example of such a conflict? I agree that current naming scheme is far from perfect, but I think that 'tablename'_partnum provides unique name for each partition.