parse partition strategy string in gram.y
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-10-21T09:32:16Z
Lists: pgsql-hackers
Attachments
- 0001-have-gram.y-resolve-partition-strategy-names.patch (text/x-diff)
Hello I've had this patch sitting in a local branch for way too long. It's a trivial thing but for some reason it bothered me: we let the partition strategy flow into the backend as a string and only parse it into the catalog 1-char version quite late. This patch makes gram.y responsible for parsing it and passing it down as a value from a new enum, which looks more neat. Because it's an enum, some "default:" cases can be removed in a couple of places. I also added a new elog() in case the catalog contents becomes broken. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "Estoy de acuerdo contigo en que la verdad absoluta no existe... El problema es que la mentira sí existe y tu estás mintiendo" (G. Lama)
Commits
-
meson: Split 'main' suite into 'regress' and 'isolation'
- a5ac3e76fe96 16.0 landed
-
Resolve partition strategy during early parsing
- 5fca91025e05 16.0 landed