Gregory Stark <stark@enterprisedb.com> writes:
> Having fixed that everything works fine with SET and WITH being reserved
> keywords. You didn't mean to say I should be able to leave WITH unreserved did
> you?
I think we'd decided that was a lost cause, unless you see a way?
> Of course that was the easy part...
Yup ;-)
regards, tom lane