Skip site navigation (1) Skip section navigation (2)

Re: byteain bug(?)

From: "Joe Conway" <joseph(dot)conway(at)home(dot)com>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: byteain bug(?)
Date: 2001-09-07 04:23:21
Message-ID: 022401c13754$d4065590$0705a8c0@jecw2k1 (view raw or flat)
Thread:
Lists: pgsql-hackers
>
> 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



In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-09-07 04:24:14
Subject: Re: byteain bug(?)
Previous:From: tomasDate: 2001-09-07 04:10:01
Subject: Re: Conditional NOTIFY is not implemented

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group