pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedRelease of DBD-pg 1.22
15+ messages / 5 participants
[nested] [flat]
* Release of DBD-pg 1.22
@ 2003-03-27 04:49 Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 15+ messages in thread
From: Bruce Momjian @ 2003-03-27 04:49 UTC (permalink / raw)
To: David Wheeler <david@wheeler.net>; +Cc: Rudy Lippan <rlippan@remotelinux.com>; Dominic Mitchell <dom@semantico.com>; pgsql-interfaces; dbi-dev@perl.org
We have just released DBD-pg 1.22. Here are the changes:
1.22 Wed Mar 26 22:33:44 EST 2003
- Win32 compile fix for snprintf [Joe Spears]
- Fix memory allocation problem in bytea escaping [Barrie Slaymaker]
- Add utf8 support [Dominic Mitchell <dom@semantico.com>]
- Transform Perl arrays into PostgreSQL arrays [Alexey Slynko]
- Fix for foreign_key_info() [Keith Keller]
- Fix PG_TEXT parameter binding
- Doc cleanups [turnstep]
- Fix warning from func($table, 'table_attributes') [turnstep]
- Added suppport for schemas [turnstep]
- Fix binary to a bytea field conversion [Chris Dunlop <chris@onthe.net.au>]
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Release of DBD-pg 1.22
@ 2003-03-28 12:15 Adam Witney <awitney@sghms.ac.uk>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 15+ messages in thread
From: Adam Witney @ 2003-03-28 12:15 UTC (permalink / raw)
To: pgsql-interfaces
Trying to install on Mac OSX 10.2.4
Everything all compiles ok, but all the tests fail with
dyld: /usr/bin/perl Undefined symbols: _is_utf8_string
Anyone know what this means?
Perl 5 5.6.0
DBI module 1.35
PostgreSQL 7.3.2
Test::Simple 0.47
Thanks for any help
Adam
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Release of DBD-pg 1.22
@ 2003-03-28 15:58 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Adam Witney <awitney@sghms.ac.uk>
0 siblings, 1 reply; 15+ messages in thread
From: Bruce Momjian @ 2003-03-28 15:58 UTC (permalink / raw)
To: Adam Witney <awitney@sghms.ac.uk>; +Cc: pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>
What version of perl do you have? I have 5.005_03, and others have 5.6,
and both seem to work. The current test in dbdimp.c is:
#ifdef SvUTF8_off
if (imp_dbh->pg_enable_utf8) {
SvUTF8_off(sv);
/* XXX Is this all the character data types? */
if (18 == type || 25 == type || 1042 ==type || 1043 == type) {
if (is_high_bit_set(val) && is_utf8_string(val, val_len))
SvUTF8_on(sv);
}
}
#endif
Maybe that isn't the right test --- maybe you have a version of perl
that passes the #ifdef test, but doesn't have is_utf8_string().
---------------------------------------------------------------------------
Adam Witney wrote:
>
> Trying to install on Mac OSX 10.2.4
>
> Everything all compiles ok, but all the tests fail with
>
> dyld: /usr/bin/perl Undefined symbols: _is_utf8_string
>
> Anyone know what this means?
>
> Perl 5 5.6.0
> DBI module 1.35
> PostgreSQL 7.3.2
> Test::Simple 0.47
>
> Thanks for any help
>
> Adam
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Release of DBD-pg 1.22
@ 2003-03-29 14:56 Adam Witney <awitney@sghms.ac.uk>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 15+ messages in thread
From: Adam Witney @ 2003-03-29 14:56 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>
On 28/3/03 3:58 pm, "Bruce Momjian" <pgman@candle.pha.pa.us> wrote:
>
> What version of perl do you have? I have 5.005_03, and others have 5.6,
> and both seem to work. The current test in dbdimp.c is:
>
> #ifdef SvUTF8_off
> if (imp_dbh->pg_enable_utf8) {
> SvUTF8_off(sv);
> /* XXX Is this all the character data types? */
> if (18 == type || 25 == type || 1042 ==type || 1043 == type) {
> if (is_high_bit_set(val) && is_utf8_string(val, val_len))
> SvUTF8_on(sv);
> }
> }
> #endif
>
> Maybe that isn't the right test --- maybe you have a version of perl
> that passes the #ifdef test, but doesn't have is_utf8_string().
>
I have perl 5.6.0. I don't know if it has is_utf8_string()... Where would I
look for this?
The output of perl -V if this helps
[mrc1-003:] adam% perl -V
Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
Platform:
osname=darwin, osvers=6.0, archname=darwin
uname='darwin fisheye 6.0 darwin kernel version 5.2: mon jun 17 09:55:14
pdt 2002; root:xnu-201-14.rootsxnu-201-14.objrelease_ppc power macintosh
powerpc '
config_args='-ds -e -Dprefix=/usr -Dccflags=-g -pipe -Dldflags='
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define
use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
Compiler:
cc='cc', optimize='-Os', gccversion=Apple cpp-precomp 6.14
cppflags='-g -pipe -pipe -fno-common -no-cpp-precomp -flat_namespace
-DHAS_TELLDIR_PROTOTYPE -fno-strict-aliasing'
ccflags ='-g -pipe -pipe -fno-common -no-cpp-precomp -flat_namespace
-DHAS_TELLDIR_PROTOTYPE -fno-strict-aliasing'
stdchar='char', d_stdstdio=undef, usevfork=true
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=8
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, usemymalloc=n, prototype=define
Linker and Libraries:
ld='cc', ldflags =''
libpth=/usr/lib
libs=-lm -lc
libc=/System/Library/Frameworks/System.framework/System, so=dylib,
useshrplib=true, libperl=libperl.dylib
Dynamic Linking:
dlsrc=dl_dyld.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags='-bundle -flat_namespace -undefined suppress'
Characteristics of this binary (from libperl):
Compile-time options: USE_LARGE_FILES
Built under darwin
Compiled at Jul 14 2002 04:04:33
%ENV:
PERL5LIB="/sw/lib/perl5"
@INC:
/sw/lib/perl5/darwin
/sw/lib/perl5
/System/Library/Perl/darwin
/System/Library/Perl
/Library/Perl/darwin
/Library/Perl
/Library/Perl
/Network/Library/Perl/darwin
/Network/Library/Perl
/Network/Library/Perl
.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Release of DBD-pg 1.22
@ 2003-03-30 22:28 Ian Barwick <barwick@gmx.net>
parent: Adam Witney <awitney@sghms.ac.uk>
0 siblings, 1 reply; 15+ messages in thread
From: Ian Barwick @ 2003-03-30 22:28 UTC (permalink / raw)
To: Adam Witney <awitney@sghms.ac.uk>; +Cc: pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
On Saturday 29 March 2003 15:56, Adam Witney wrote:
> On 28/3/03 3:58 pm, "Bruce Momjian" <pgman@candle.pha.pa.us> wrote:
> > What version of perl do you have? I have 5.005_03, and others have 5.6,
> > and both seem to work. The current test in dbdimp.c is:
> >
> > #ifdef SvUTF8_off
> > if (imp_dbh->pg_enable_utf8) {
> > SvUTF8_off(sv);
> > /* XXX Is this all the character data types? */
> > if (18 == type || 25 == type || 1042 ==type || 1043 == type) {
> > if (is_high_bit_set(val) && is_utf8_string(val, val_len))
> > SvUTF8_on(sv);
> > }
> > }
> > #endif
> >
> > Maybe that isn't the right test --- maybe you have a version of perl
> > that passes the #ifdef test, but doesn't have is_utf8_string().
>
> I have perl 5.6.0. I don't know if it has is_utf8_string()... Where would I
> look for this?
I'm fuzzy on the details but ISTR Perl 5.6.0 was not one of Perl's better
releases and was replaced fairly quickly with 5.6.1. A bit of googling
returns is_utf8_string() together with 5.6.1 but no references to 5.6. This
is not scientific evidence though.
Can you do "perldoc perlapi" with 5.6.0? If so the presence / absence
of is_utf8_string() should solve the problem.
Ian Barwick
barwick@gmx.net
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Release of DBD-pg 1.22
@ 2003-03-31 09:28 Adam Witney <awitney@sghms.ac.uk>
parent: Ian Barwick <barwick@gmx.net>
0 siblings, 1 reply; 15+ messages in thread
From: Adam Witney @ 2003-03-31 09:28 UTC (permalink / raw)
To: Ian Barwick <barwick@gmx.net>; +Cc: pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
On 30/3/03 11:28 pm, "Ian Barwick" <barwick@gmx.net> wrote:
> On Saturday 29 March 2003 15:56, Adam Witney wrote:
>> On 28/3/03 3:58 pm, "Bruce Momjian" <pgman@candle.pha.pa.us> wrote:
>>> What version of perl do you have? I have 5.005_03, and others have 5.6,
>>> and both seem to work. The current test in dbdimp.c is:
>>>
>>> #ifdef SvUTF8_off
>>> if (imp_dbh->pg_enable_utf8) {
>>> SvUTF8_off(sv);
>>> /* XXX Is this all the character data types? */
>>> if (18 == type || 25 == type || 1042 ==type || 1043 == type) {
>>> if (is_high_bit_set(val) && is_utf8_string(val, val_len))
>>> SvUTF8_on(sv);
>>> }
>>> }
>>> #endif
>>>
>>> Maybe that isn't the right test --- maybe you have a version of perl
>>> that passes the #ifdef test, but doesn't have is_utf8_string().
>>
>> I have perl 5.6.0. I don't know if it has is_utf8_string()... Where would I
>> look for this?
>
> I'm fuzzy on the details but ISTR Perl 5.6.0 was not one of Perl's better
> releases and was replaced fairly quickly with 5.6.1. A bit of googling
> returns is_utf8_string() together with 5.6.1 but no references to 5.6. This
> is not scientific evidence though.
>
> Can you do "perldoc perlapi" with 5.6.0? If so the presence / absence
> of is_utf8_string() should solve the problem.
Yep, there is no trace of is_utf8_string() in perldoc perlapi for 5.6.0
Does this mean that my only option is to upgrade perl? Or will the module
still work without it?
Thanks for your help
adam
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Release of DBD-pg 1.22
@ 2003-03-31 23:49 Rudy Lippan <rlippan@remotelinux.com>
parent: Adam Witney <awitney@sghms.ac.uk>
0 siblings, 1 reply; 15+ messages in thread
From: Rudy Lippan @ 2003-03-31 23:49 UTC (permalink / raw)
To: Adam Witney <awitney@sghms.ac.uk>; +Cc: Ian Barwick <barwick@gmx.net>; pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
On Mon, 31 Mar 2003, Adam Witney wrote:
> Yep, there is no trace of is_utf8_string() in perldoc perlapi for 5.6.0
>
That sounds about right.
> Does this mean that my only option is to upgrade perl? Or will the module
> still work without it?
You can either upgrade perl to 5.6.1 or, if you don't want to upgrade
perl, you can dike out the section of code between the #ifdef and #endif
and then it should work (might fail some UTF-8 test). I would recommed
upgrading perl, however.
-r
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Release of DBD-pg 1.22
@ 2003-04-08 09:10 Adam Witney <awitney@sghms.ac.uk>
parent: Rudy Lippan <rlippan@remotelinux.com>
0 siblings, 2 replies; 15+ messages in thread
From: Adam Witney @ 2003-04-08 09:10 UTC (permalink / raw)
To: Rudy Lippan <rlippan@remotelinux.com>; +Cc: Ian Barwick <barwick@gmx.net>; pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
> On Mon, 31 Mar 2003, Adam Witney wrote:
>
>> Yep, there is no trace of is_utf8_string() in perldoc perlapi for 5.6.0
>>
>
> That sounds about right.
>
>> Does this mean that my only option is to upgrade perl? Or will the module
>> still work without it?
>
> You can either upgrade perl to 5.6.1 or, if you don't want to upgrade
> perl, you can dike out the section of code between the #ifdef and #endif
> and then it should work (might fail some UTF-8 test). I would recommed
> upgrading perl, however.
Ok, I have upgraded to perl 5.6.1, but now make test gives this
.....
t/03bind............ok
t/04execute.........ok 9/13*** malloc[20356]: error for object 0x235c20:
Incorrect checksum for freed object - object was probably modified after
being freed; break at szone_error
*** malloc[20356]: error for object 0x235c20: Incorrect checksum for freed
object - object was probably modified after being freed; break at
szone_error
t/04execute.........dubious
Test returned status 0 (wstat 11, 0xb)
DIED. FAILED tests 10-13
Failed 4/13 tests, 69.23% okay
t/05fetch...........ok, 3/10 skipped: need Encode module for unicode tests
t/06disconnect......ok
t/07reuse...........ok
t/08txn.............ok
t/09autocommit......ok
t/11quoting.........ok
t/12placeholders....ok
t/13pgtype..........ok
t/15funct...........ok 4/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 5/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 6/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 808.
t/15funct...........ok 25/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 26/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 28/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 605.
t/15funct...........ok 31/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 32/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 33/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 34/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 35/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 36/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 701.
t/15funct...........ok 37/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 38/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 39/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 40/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 41/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 42/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 43/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 44/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 45/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 46/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 47/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 48/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 49/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 50/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 203.
t/15funct...........ok 53/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 291.
t/15funct...........ok 54/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 291.
t/15funct...........ok 56/59Argument "7.3.2" isn't numeric in numeric lt (<)
at blib/lib/DBD/Pg.pm line 291.
t/15funct...........ok, 7/59 skipped: various reasons
t/99cleanup.........ok
Failed Test Status Wstat Total Fail Failed List of Failed
----------------------------------------------------------------------------
----
t/04execute.t 0 11 13 4 30.77% 10-13
10 subtests skipped.
Failed 1/17 test scripts, 94.12% okay. 4/186 subtests failed, 97.85% okay.
make: *** [test_dynamic] Error 255
Any ideas whats happening now?
Thanks
Adam
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: [Dbdpg-general] Re: Release of DBD-pg 1.22
@ 2003-04-08 13:29 greg@turnstep.com
parent: Adam Witney <awitney@sghms.ac.uk>
1 sibling, 1 reply; 15+ messages in thread
From: greg@turnstep.com @ 2003-04-08 13:29 UTC (permalink / raw)
To: dbdpg-general@gborg.postgresql.org; +Cc: pgsql-interfaces; awitney@sghms.ac.uk
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Ok, I have upgraded to perl 5.6.1, but now make test gives this
I am not sure about the malloc errors, but the "isn't numeric" errors
should be fixed by grabbing an updated version of DBD::Pg.
By the way, the latest stable version of perl is 5.8.0. You may want
to consider jumping to that as long as you are upgrading.
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200304080926
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+ks6evJuQZxSWSsgRAmcLAKCdRHIB+XGQH/VGUmtEK8vwFiuYkQCfV/CE
9Ga23giFd4I+iZ0pzF1XvvM=
=jzS7
-----END PGP SIGNATURE-----
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: [Dbdpg-general] Re: Release of DBD-pg 1.22
@ 2003-04-08 13:32 Rudy Lippan <rlippan@remotelinux.com>
parent: Adam Witney <awitney@sghms.ac.uk>
1 sibling, 1 reply; 15+ messages in thread
From: Rudy Lippan @ 2003-04-08 13:32 UTC (permalink / raw)
To: Adam Witney <awitney@sghms.ac.uk>; +Cc: Rudy Lippan <rlippan@remotelinux.com>; Ian Barwick <barwick@gmx.net>; pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
On Tue, 8 Apr 2003, Adam Witney wrote:
> .....
> t/03bind............ok
> t/04execute.........ok 9/13*** malloc[20356]: error for object 0x235c20:
> Incorrect checksum for freed object - object was probably modified after
> being freed; break at szone_error
> *** malloc[20356]: error for object 0x235c20: Incorrect checksum for freed
> object - object was probably modified after being freed; break at
> szone_error
> t/04execute.........dubious
> Test returned status 0 (wstat 11, 0xb)
> DIED. FAILED tests 10-13
> Failed 4/13 tests, 69.23% okay
I do not like the looks of this. Did this test fail with DBD::Pg 1.21?
> at blib/lib/DBD/Pg.pm line 291.
> t/15funct...........ok 56/59Argument "7.3.2" isn't numeric in numeric lt (<)
> at blib/lib/DBD/Pg.pm line 291.
I ran into this on my system also. There is a if $version >7.x where I
can't remember what x is. Anyway the regex that pulls version gets "7.3.2"
which can't be used as a number so perl warns you. I will write up a
patch for this later today. Grrr.
-r
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: [Dbdpg-general] Re: Release of DBD-pg 1.22
@ 2003-04-08 13:50 Adam Witney <awitney@sghms.ac.uk>
parent: greg@turnstep.com
0 siblings, 1 reply; 15+ messages in thread
From: Adam Witney @ 2003-04-08 13:50 UTC (permalink / raw)
To: greg@turnstep.com; dbdpg-general@gborg.postgresql.org; +Cc: pgsql-interfaces
> I am not sure about the malloc errors, but the "isn't numeric" errors
> should be fixed by grabbing an updated version of DBD::Pg.
This is DBD-Pg-1.22, do you mean newer than that?
> By the way, the latest stable version of perl is 5.8.0. You may want
> to consider jumping to that as long as you are upgrading.
The only thing is that I have heard suggestions that replacing the stock
perl on OS X with 5.8 can cause problems with certain system functions
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: [Dbdpg-general] Re: Release of DBD-pg 1.22
@ 2003-04-08 13:55 Adam Witney <awitney@sghms.ac.uk>
parent: Rudy Lippan <rlippan@remotelinux.com>
0 siblings, 1 reply; 15+ messages in thread
From: Adam Witney @ 2003-04-08 13:55 UTC (permalink / raw)
To: Rudy Lippan <rlippan@remotelinux.com>; +Cc: Ian Barwick <barwick@gmx.net>; pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
On 8/4/03 2:32 pm, "Rudy Lippan" <rlippan@remotelinux.com> wrote:
> On Tue, 8 Apr 2003, Adam Witney wrote:
>
>> .....
>> t/03bind............ok
>> t/04execute.........ok 9/13*** malloc[20356]: error for object 0x235c20:
>> Incorrect checksum for freed object - object was probably modified after
>> being freed; break at szone_error
>> *** malloc[20356]: error for object 0x235c20: Incorrect checksum for freed
>> object - object was probably modified after being freed; break at
>> szone_error
>> t/04execute.........dubious
>> Test returned status 0 (wstat 11, 0xb)
>> DIED. FAILED tests 10-13
>> Failed 4/13 tests, 69.23% okay
>
> I do not like the looks of this. Did this test fail with DBD::Pg 1.21?
Just downloaded, built and tested DBD-Pg-1.21 with no problems.
>> at blib/lib/DBD/Pg.pm line 291.
>> t/15funct...........ok 56/59Argument "7.3.2" isn't numeric in numeric lt (<)
>> at blib/lib/DBD/Pg.pm line 291.
>
> I ran into this on my system also. There is a if $version >7.x where I
> can't remember what x is. Anyway the regex that pulls version gets "7.3.2"
> which can't be used as a number so perl warns you. I will write up a
> patch for this later today. Grrr.
I had a look myself... Its this one
$version < 7.3
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: [Dbdpg-general] Re: Release of DBD-pg 1.22
@ 2003-04-08 14:03 greg@turnstep.com
parent: Adam Witney <awitney@sghms.ac.uk>
0 siblings, 0 replies; 15+ messages in thread
From: greg@turnstep.com @ 2003-04-08 14:03 UTC (permalink / raw)
To: dbdpg-general@gborg.postgresql.org; +Cc: awitney@sghms.ac.uk; pgsql-interfaces
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> I am not sure about the malloc errors, but the "isn't numeric" errors
>> should be fixed by grabbing an updated version of DBD::Pg.
> This is DBD-Pg-1.22, do you mean newer than that?
Yes, sorry I was not clear. The latest CVS version should cleanly work
around the versioning problem. In particular, you should be able to
replace just the file "Pg.pm" to fix that problem:
http://gborg.postgresql.org/project/dbdpg/cvs/cvs.php/dbdpg
>> By the way, the latest stable version of perl is 5.8.0. You may want
>> to consider jumping to that as long as you are upgrading.
> The only thing is that I have heard suggestions that replacing the stock
> perl on OS X with 5.8 can cause problems with certain system functions
Forgot about the OS X factor. Nevermind. :) You want 5.6.1r2.
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200304080959
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+ktaVvJuQZxSWSsgRAmfbAKCaBsg82LsLGry5HJ+iP0qUfJtcQACfcm4C
8q0kk3kTJEZgGVz16JzW+/Q=
=3Lw2
-----END PGP SIGNATURE-----
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: [Dbdpg-general] Re: Release of DBD-pg 1.22
@ 2003-04-09 03:26 Rudy Lippan <rlippan@remotelinux.com>
parent: Adam Witney <awitney@sghms.ac.uk>
0 siblings, 1 reply; 15+ messages in thread
From: Rudy Lippan @ 2003-04-09 03:26 UTC (permalink / raw)
To: Adam Witney <awitney@sghms.ac.uk>; +Cc: Ian Barwick <barwick@gmx.net>; pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
On Tue, 8 Apr 2003, Adam Witney wrote:
> >> t/03bind............ok
> >> t/04execute.........ok 9/13*** malloc[20356]: error for object 0x235c20:
> >> Incorrect checksum for freed object - object was probably modified after
> >> being freed; break at szone_error
> >> *** malloc[20356]: error for object 0x235c20: Incorrect checksum for freed
> >> object - object was probably modified after being freed; break at
> >> szone_error
> >> t/04execute.........dubious
> >> Test returned status 0 (wstat 11, 0xb)
> >> DIED. FAILED tests 10-13
> >> Failed 4/13 tests, 69.23% okay
> >
> > I do not like the looks of this. Did this test fail with DBD::Pg 1.21?
>
> Just downloaded, built and tested DBD-Pg-1.21 with no problems.
>
I don't see why 1.21 should work while 1.22 failes, so all I can say is
If 1.21 works, use it. If you see this 1.21, you might want to
try what is in CVS because much of the prepare, quoting and execute code
was rewritten and might have fixed the issue.
> > I ran into this on my system also. There is a if $version >7.x where I
> > can't remember what x is. Anyway the regex that pulls version gets "7.3.2"
> > which can't be used as a number so perl warns you. I will write up a
> > patch for this later today. Grrr.
>
> I had a look myself... Its this one
>
> $version < 7.3
>
Yup, looks like someone put in a patch to fix that already.
-r
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: [Dbdpg-general] Re: Release of DBD-pg 1.22
@ 2003-04-09 11:47 Adam Witney <awitney@sghms.ac.uk>
parent: Rudy Lippan <rlippan@remotelinux.com>
0 siblings, 0 replies; 15+ messages in thread
From: Adam Witney @ 2003-04-09 11:47 UTC (permalink / raw)
To: Rudy Lippan <rlippan@remotelinux.com>; +Cc: Ian Barwick <barwick@gmx.net>; pgsql-interfaces; DBD-pg <dbdpg-general@gborg.postgresql.org>; Bruce Momjian <pgman@candle.pha.pa.us>
On 9/4/03 4:26 am, "Rudy Lippan" <rlippan@remotelinux.com> wrote:
> On Tue, 8 Apr 2003, Adam Witney wrote:
>
>>>> t/03bind............ok
>>>> t/04execute.........ok 9/13*** malloc[20356]: error for object 0x235c20:
>>>> Incorrect checksum for freed object - object was probably modified after
>>>> being freed; break at szone_error
>>>> *** malloc[20356]: error for object 0x235c20: Incorrect checksum for freed
>>>> object - object was probably modified after being freed; break at
>>>> szone_error
>>>> t/04execute.........dubious
>>>> Test returned status 0 (wstat 11, 0xb)
>>>> DIED. FAILED tests 10-13
>>>> Failed 4/13 tests, 69.23% okay
>>>
>>> I do not like the looks of this. Did this test fail with DBD::Pg 1.21?
>>
>> Just downloaded, built and tested DBD-Pg-1.21 with no problems.
>>
>
> I don't see why 1.21 should work while 1.22 failes, so all I can say is
> If 1.21 works, use it. If you see this 1.21, you might want to
> try what is in CVS because much of the prepare, quoting and execute code
> was rewritten and might have fixed the issue.
The only problem is I wanted to try out the "Transform Perl arrays into
PostgreSQL arrays" feature in 1.22
Ok, so have tried the make test again and now I get this
t/04execute.........ok 9/13Attempt to free non-existent shared string at
t/04execute.t line 87.
t/04execute.........dubious
Test returned status 0 (wstat 10, 0xa)
DIED. FAILED tests 10-13
Failed 4/13 tests, 69.23% okay
Have been building apache and mod_perl in between (presumably irrelevent for
this?) and have of course had several restarts of the machine (laptop)... So
apart from this nothing else should have changed.
Does this help finding the problem?
Thanks
adam
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 15+ messages in thread
end of thread, other threads:[~2003-04-09 11:47 UTC | newest]
Thread overview: 15+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-03-27 04:49 Release of DBD-pg 1.22 Bruce Momjian <pgman@candle.pha.pa.us>
2003-03-28 12:15 ` Adam Witney <awitney@sghms.ac.uk>
2003-03-28 15:58 ` Bruce Momjian <pgman@candle.pha.pa.us>
2003-03-29 14:56 ` Adam Witney <awitney@sghms.ac.uk>
2003-03-30 22:28 ` Ian Barwick <barwick@gmx.net>
2003-03-31 09:28 ` Adam Witney <awitney@sghms.ac.uk>
2003-03-31 23:49 ` Rudy Lippan <rlippan@remotelinux.com>
2003-04-08 09:10 ` Adam Witney <awitney@sghms.ac.uk>
2003-04-08 13:29 ` greg@turnstep.com
2003-04-08 13:50 ` Adam Witney <awitney@sghms.ac.uk>
2003-04-08 14:03 ` greg@turnstep.com
2003-04-08 13:32 ` Rudy Lippan <rlippan@remotelinux.com>
2003-04-08 13:55 ` Adam Witney <awitney@sghms.ac.uk>
2003-04-09 03:26 ` Rudy Lippan <rlippan@remotelinux.com>
2003-04-09 11:47 ` Adam Witney <awitney@sghms.ac.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox