| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Maxim Orlov <m(dot)orlov(at)postgrespro(dot)ru> |
| Cc: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amul Sul <sulamul(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Automatic HASH and LIST partition creation |
| Date: | 2020-12-22 14:29:56 |
| Message-ID: | alpine.DEB.2.22.394.2012221025000.533489@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> CREATE TABLE foo(a int) PARTITION BY LIST(a) CONFIGURATION (FOR VALUES IN
> (1,2),(3,4) DEFAULT PARTITION foo_def);
I would like to disagree with this syntactic approach because it would
very specific to each partition method. IMHO the syntax should be as
generic as possible. I'd suggest (probably again) a keyword/value list
which would allow to be quite adaptable without inducing any pressure on
the parser.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-12-22 14:58:33 | Re: Deadlock between backend and recovery may not be detected |
| Previous Message | Bharath Rupireddy | 2020-12-22 13:31:09 | EXPLAIN/EXPLAIN ANALYZE REFRESH MATERIALIZED VIEW |