Re: byteain() doesn't parse correctly

Jered Floyd <jered@permabit.com> writes:
> More curious is that it can't handle '\134' either, implying that 
> multiple levels of parsing are going on.

You're right, there are multiple levels of parsing going on.  The
string-literal parser gets first crack before the type-specific
input converter does.  If you don't allow for that when counting
backslashes etc, you'll get confused for sure.

			regards, tom lane