Re: byteain bug(?)

>
> Should be fixed.  I noticed this myself.  Should we require three digits?
>
>
> > I just noticed some unexpected behavior from byteain:
> >
> >
> > test=# select '\\009'::bytea;
> >  ?column?
> > ----------
> >  \011
> > (1 row)

<snip>

> >
> > It checks for a '\' followed by three digits, but does not attempt to
> > enforce that the three digits actually produce a valid octal number.
Anyone
> > object to me fixing this?
> >

Based on the thread this morning on patches, I was thinking we should allow
'\\', '\0', or '\###' where ### is any valid octal. At least that's what I
was going to have decode(bytea, 'escape') handle.

-- Joe