Re: byteain() doesn't parse correctly - Mailing list pgsql-bugs

From Tom Lane
Subject Re: byteain() doesn't parse correctly
Date
Msg-id 28091.981557975@sss.pgh.pa.us
Whole thread Raw
In response to byteain() doesn't parse correctly  (Jered Floyd <jered@permabit.com>)
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG or feature?
Next
From: William Boyle
Date:
Subject: Re: round - timestamp bug