-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
Tom Lane writes:
> Olleg <[EMAIL PROTECTED]> writes:
> > It's bug, autoconf headers may not be included in "library headers".
>
> If you think it's a bug you'd better complain to the autoconf people.
> pg_config.h is generated entirely by autoconf tools.
Admittedly, you're not supposed to install
-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(
Joseph Tate <[EMAIL PROTECTED]> writes:
> (gdb) where
> #0 0xb69f7987 in CC_send_function () from /usr/lib/libodbcpsql.so.2
> #1 0xb6a06940 in lo_creat () from /usr/lib/libodbcpsql.so.2
> #2 0xb69c6c23 in lo_import () from /usr/lib/libpq.so.3
> #3 0xb69e4121 in zif_pg_lo_import (ht=2, return_va
When using "pg_restore -S postgres -s -vcd DBNAME bkupfile" on an
existing database, I get the following error:
pg_restore: connecting to database for restore
pg_restore: dropping RULE au_d_assigned_template
pg_restore: dropping RULE au_u_assigned_template
... More rules, triggers, constraints, ind
I'm not really sure how to go about debugging this, but when I use PHP
to create large objects using libpq, with the php odbc module installed,
I get the following seg fault:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226627936 (LWP 28034)]
0xb69f7987 in CC_send_fun
Olleg <[EMAIL PROTECTED]> writes:
> olleg=# \set AUTOCOMMIT OFF
It has to be
\set AUTOCOMMIT off
Not sure if we should be more flexible about this or not. The code says
/*
* for backwards compatibility, anything except "off" is taken as
* "true"
*/
Olleg <[EMAIL PROTECTED]> writes:
> It's bug, autoconf headers may not be included in "library headers".
If you think it's a bug you'd better complain to the autoconf people.
pg_config.h is generated entirely by autoconf tools.
regards, tom lane
--
SuSE Linux 8.2 (i586)
PostgreSQL REL7_4_STABLE (cvs), 7.4
compiled with:
gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux)
flex version 2.5.4
bison (GNU Bison) 1.875
PostgreSQL config.status 7.4
configured by ./configure, generated by GNU Autoconf 2.53,
with options "'--prefix=/opt/pgsql' '--enabl
SuSE Linux 8.2 (i586)
PostgreSQL REL7_4_STABLE (cvs), 7.4
compiled with:
gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux)
flex version 2.5.4
bison (GNU Bison) 1.875
PostgreSQL config.status 7.4
configured by ./configure, generated by GNU Autoconf 2.53,
with options "'--prefix=/opt/pgsql' '--enabl
13 matches
Mail list logo
