| From: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Date: | 2024-05-11 13:19:38 |
| Message-ID: | ba30b3da-e146-4ec4-a06f-3c7e4b34cecd@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
11.05.2024 12:00, Alexander Lakhin wrote:
> Please look at one more anomaly with temporary tables:
Thank you, Alexander!
The problem affects the SPLIT PARTITION command.
CREATE TEMP TABLE t (a int) PARTITION BY RANGE (a);
CREATE TEMP TABLE tp_0 PARTITION OF t FOR VALUES FROM (0) TO (2) ;
-- ERROR: relation "tp_0" already exists
ALTER TABLE t SPLIT PARTITION tp_0 INTO
(PARTITION tp_0 FOR VALUES FROM (0) TO (1), PARTITION tp_1 FOR
VALUES FROM (1) TO (2));
I'll try to fix it soon.
--
With best regards,
Dmitry Koval
Postgres Professional: http://postgrespro.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-05-11 13:57:49 | Re: First draft of PG 17 release notes |
| Previous Message | aa | 2024-05-11 12:19:49 | Is there any chance to get some kind of a result set sifting mechanism in Postgres? |