| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
| Cc: | Maxim Orlov <m(dot)orlov(at)postgrespro(dot)ru>, 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 20:50:36 |
| Message-ID: | alpine.DEB.2.22.394.2012221643050.533489@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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'd rather use an automatic tool (lexer/parser) if possible instead of
doing it by hand if I can. If you want a really nice syntax with clever
tricks, then you may need to switch to manual though, but pg/sql is not in
that class.
> I think both are possible but my predisposition was that we'd better use
> the later if possible.
I agree.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-12-22 21:13:06 | Re: Proposed patch for key managment |
| Previous Message | Tom Lane | 2020-12-22 20:46:27 | Re: libpq compression |