On Sun, Jul 19, 2015 at 4:16 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Josh Berkus <j...@agliodbs.com> writes: >> On 07/17/2015 04:36 PM, Jim Nasby wrote: >>> I'm guessing it'd be really ugly/hard to support at least this GUC being >>> multi-line? > >> Mind you, multi-line GUCs would be useful otherwise, but we don't want >> to hinge this feature on making that work. > > I'm pretty sure that changing the GUC parser to allow quoted strings to > continue across lines would be trivial. The problem with it is not that > it's hard, it's that omitting a closing quote mark would then result in > the entire file being syntactically broken, with the error message(s) > almost certainly pointing somewhere else than where the actual mistake is. > Do we really want such a global reduction in friendliness to make this > feature easier?
Maybe shoehorning this into the GUC mechanism is the wrong thing, and what we really need is a new config file for this. The information we're proposing to store seems complex enough to justify that. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
