-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Joe Conway <[EMAIL PROTECTED]> wrote:
> Note that bytea input strings should be escaped with doubled backslashes,
> because the string literal parser consumes 1 layer, and the byteain
> function consumes another. See:
> http://www.postgresql
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Alvar Freude <[EMAIL PROTECTED]> wrote:
> there is a bug in handling bytea columns with index and the like-operator.
> At least in 7.3.4. When the FreeBSD Port for 7.4 is ready, I'll test this
> ... ;-)
sorry, shame on me: I have to put two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Joe Conway <[EMAIL PROTECTED]> wrote:
>
> Note that bytea input strings should be escaped with doubled backslashes,
> because the string literal parser consumes 1 layer, and the byteain
> function consumes another. See:
> http://www.postgre
Alvar Freude wrote:
PostgreSQL 7.3.4 on i386-portbld-freebsd4.8, compiled by GCC 2.95.4
begin;
create table test (b bytea);
create index tst_idx on test(b);
insert into test values ('\001abc\006');
insert into test values ('\001xabc\006');
insert into test values ('\001\002abc\006')
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
there is a bug in handling bytea columns with index and the like-operator.
At least in 7.3.4. When the FreeBSD Port for 7.4 is ready, I'll test this
... ;-)
When an index scan is active, a query dosn't give the correct result:
select version(
