> On Dec 12, 2015, at 9:40 PM, Tom Lane <[email protected]> wrote: > > Mark Dilger <[email protected]> writes: >>> On Dec 12, 2015, at 3:42 PM, Tom Lane <[email protected]> wrote: >>> ... In general, though, I'd rather not try to >>> teach InteractiveBackend() such a large amount about SQL syntax. > >> I use CREATE RULE within startup files in the fork that I maintain. I have >> lots of them, totaling perhaps 50k lines of rule code. I don't think any of >> that >> code would have a problem with the double-newline separation you propose, >> which seems a more elegant solution to me. > > Yeah? Just for proof-of-concept, could you run your startup files with > the postgres.c patch as proposed, and see whether you get any failures?
Given all the changes I've made to initdb.c in my fork, that patch of yours doesn't apply. mark -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
