Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
| От | Alexander Lakhin |
|---|---|
| Тема | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Дата | |
| Msg-id | 5dee3937-8e9f-cca4-11fb-737709a92b37@gmail.com обсуждение исходный текст |
| Ответ на | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands (Alexander Korotkov <aekorotkov@gmail.com>) |
| Ответы |
Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
Re: Add SPLIT PARTITION/MERGE PARTITIONS commands Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Список | pgsql-hackers |
Hi Alexander, 18.04.2024 13:35, Alexander Korotkov wrote: > > The revised patchset is attached. > 1) I've split the fix for the CommandCounterIncrement() issue and the > fix for relation persistence issue into a separate patch. > 2) I've validated that the lock on the new partition is held in > createPartitionTable() after ProcessUtility() as pointed out by > Robert. So, no need to place the lock again. > 3) Added fix for problematic error message as a separate patch [1]. > 4) Added rename "salemans" => "salesmen" for tests as a separate patch. > > I think these fixes are reaching committable shape, but I'd like > someone to check it before I push. I think the feature implementation should also provide tab completion for SPLIT/MERGE. (ALTER TABLE t S<Tab> fills in only SET now.) Also, the following MERGE operation: CREATE TABLE t (i int, PRIMARY KEY(i)) PARTITION BY RANGE (i); CREATE TABLE tp_0 PARTITION OF t FOR VALUES FROM (0) TO (1); CREATE TABLE tp_1 PARTITION OF t FOR VALUES FROM (1) TO (2); ALTER TABLE t MERGE PARTITIONS (tp_0, tp_1) INTO tp_0; leaves a strange constraint: \d+ t* Table "public.tp_0" ... Not-null constraints: "merge-16385-26BCB0-tmp_i_not_null" NOT NULL "i" Best regards, Alexander
В списке pgsql-hackers по дате отправления: