koyae

Here's the blueprint. This burns down any evil tricks I can come up with.  I'll probably do a naïve implementation first (just reading one character at a...

To address your points: - Yes. C-like block comments started with `/*` do indeed come to an end with `*/`, sorry; I had a typo where I'd notated it as...

I forgot to state it in my commit-comment, but 46573e8 fixes this issue.

Although I did end up stripping the contents of end-of-line `--` comments, I discovered that expressions like `/*/**/` are indeed syntax errors, at least when tested against Postgres 9.4: ```...

Once #14 looks like it's down for the count, we can circle around to the remaining transitions which deal with with `psql` directives. 

Old tests are now passing as of 46573e8. The following commit (0dd9de2) passes the same tests, plus the ones it adds.

**On _performance:_** Just did a quick benchmark and it looks like the earlier 92d4bfe runs for about 56 seconds on a 56MB file whereas the latest commit (0dd9de2) runs in...

Work and life in general have been a little nuts lately, but a belated "yep" on planning to do optimization on this. Similar to the way you'd been doing it...

I've gotten the memory-issues under control a bit better now, I believe. Speed-wise, on the same 60MB file I mentioned [earlier](https://github.com/markdrago/pgsanity/pull/13#issuecomment-222433982), processing now completes in just a hair less than...

Hey again! Thanks for your patience on all this. Let me try to answer some of your questions. ### Avoiding need for optional commandline flags: That's a toughie; obviously, pgsanity...