Re: [PATCH] Automatic HASH and LIST partition creation
Pavel Borisov <pashkin.elfe@gmail.com>
From: Pavel Borisov <pashkin.elfe@gmail.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Maxim Orlov <m.orlov@postgrespro.ru>, Anastasia Lubennikova <a.lubennikova@postgrespro.ru>,
Rahila Syed <rahilasyed90@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Justin Pryzby <pryzby@telsasoft.com>, Robert Haas <robertmhaas@gmail.com>, Amul Sul <sulamul@gmail.com>
Date: 2020-12-22T15:58:13Z
Lists: pgsql-hackers
> > Why? We could accept anything in the list? i.e.: > > (ident =? value[, ident =? value]*) > > > I don't against this but as far as I've heard there is some > > opposition among PG community against new keywords. Maybe I am wrong. > > the ident is a keyword that can be interpreted later on, not a "reserved > keyword" from a parser perspective, which is the only real issue? > > The parser does not need to know about it, only the command interpreter > which will have to interpret it. AUTOMATIC is a nice parser cue to > introduce such a ident-value list. > > > 2. The existing syntax for declarative partitioning is different to your > > proposal. > > Yep. I think that it was not so good a design choice from a > language/extensibility perspective. > Thank you very much, Fabien. It is clear enough. BTW could you tell me a couple of words about pros and cons of c-code syntax parsing comparing to parsing using gram.y trees? I think both are possible but my predisposition was that we'd better use the later if possible. Best regards, Pavel Borisov >
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove complaints about COLLATE clauses in partition bound values.
- 2dfa3fea88bc 14.0 cited