Re: [PATCH] Automatic HASH and LIST partition creation
| От | Pavel Borisov |
|---|---|
| Тема | Re: [PATCH] Automatic HASH and LIST partition creation |
| Дата | |
| Msg-id | CALT9ZEFZ=BtOm7pfVNXzjDHJ01Vpv=P=QmXVxGVAgS5NHcOPCQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] Automatic HASH and LIST partition creation (Fabien COELHO <coelho@cri.ensmp.fr>) |
| Список | pgsql-hackers |
My 0.02 €: What I think does not matter much, what committers think is the
way to pass something. However, I do not think that such an idea would
pass a committer:-)
The same idea was the reason for my proposal to make automatic partitioning clauses to be in accordance with existing declarative syntax (even if it seems little bit long to write words "configuration (for values" )
CREATE TABLE foo(a int) PARTITION BY LIST(a) CONFIGURATION (FOR VALUES
IN (1,2),(3,4) DEFAULT PARTITION foo_def);
CREATE TABLE foo(a int) PARTITION BY HASH(a) CONFIGURATION (FOR VALUES
WITH MODULUS 3);
CREATE TABLE foo(a int) PARTITION BY RAGE(a) CONFIGURATION (FOR VALUES
FROM 1 TO 1000 INTERVAL 10 DEFAULT PARTITION foo_def)
IN (1,2),(3,4) DEFAULT PARTITION foo_def);
CREATE TABLE foo(a int) PARTITION BY HASH(a) CONFIGURATION (FOR VALUES
WITH MODULUS 3);
CREATE TABLE foo(a int) PARTITION BY RAGE(a) CONFIGURATION (FOR VALUES
FROM 1 TO 1000 INTERVAL 10 DEFAULT PARTITION foo_def)
If we want generic (ident = value,...) then we need to introduce different to what is already committed for manual partitioning which I considered worse than my proposal above. Still other opinions are highly valued.
--
В списке pgsql-hackers по дате отправления: