Horton
Menu

Re: [PATCH] Automatic HASH and LIST partition creation

Fabien COELHO <coelho@cri.ensmp.fr>

View thread
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Pavel Borisov <pashkin.elfe@gmail.com>
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-22T20:50:36Z
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.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove complaints about COLLATE clauses in partition bound values.