=?utf-8?q?=D0=A7=D1=83=D0=BC=D0=B0=D0=BA_=D0=90=D0=BD=D1=82=D0=BE=D0=BD?= <a(dot)chumak(at)postgrespro(dot)ru> writes:
> This patch adds a unified mechanism for declaring and using composite configuration options in GUC, eliminating the need to write a custom parser for each new complex data type. New syntax for end user is json-like.
TBH, I think this is a bad idea altogether. GUCs that would need
this are probably poorly designed in the first place; we should not
encourage inventing more. I also don't love adding thousands of
lines of code without any use-case at hand.
regards, tom lane