Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg - Mailing list pgsql-interfaces

Brandon,

could you let us know YOUR  results with DBD::Pg 1.41 with and w/o
 that I've posted earlier? I just did some surface-deep testing
here and here is what I've found:

DBD-1.40 - slow 
DBD-1.41 - fast
DBD-1.41, ed - fast. I  can't see difference between ed and
non ed.

so it actually turned out that stock 1.41 already has that problem
fixed... Though using UNKNOWN instead of VARCHAR for cases when no
type was supplied (as Tom Lane suggested) is still a good idea, I
think. My  needs to be careful reviewed - I'm not familiar with
DBD:Pg on a deep enough level to gurantee that it's not screwing
anything.

On Apr 8, 2005 4:24 PM, Vlad <[email protected]> wrote:
> Brandon,
> 
> try this  instead.
> 
> diff -ru DBD-Pg-1.41/dbdimp.c DBD-Pg-1.41-ed/dbdimp.c
> --- DBD-Pg-1.41/dbdimp.c        Fri Apr  8 16:06:12 2005
> +++ DBD-Pg-1.41-ed/dbdimp.c        Fri Apr  8 15:46:50 2005
> @@ -1415,7 +1415,7 @@
>         }
>         else if (NULL == currph->bind_type) { /* "sticky" data type */
>                 /* This is the default type, but we will honor
> defaultval if we can */
> -               currph->bind_type = pg_type_data(VARCHAROID);
> +               currph->bind_type = pg_type_data(UNKNOWNOID);
>                 if (!currph->bind_type)
>                         croak("Default type is bad!!!!???");
>         }
> diff -ru DBD-Pg-1.41/types.c DBD-Pg-1.41-ed/types.c
> --- DBD-Pg-1.41/types.c Fri Apr  8 16:06:23 2005
> +++ DBD-Pg-1.41-ed/types.c Fri Apr  8 15:46:37 2005
> @@ -55,7 +55,7 @@
>         {ABSTIMEOID, "abstime", DBDPG_TRUE, null_quote, null_dequote, {0}},
>         {RELTIMEOID, "reltime", DBDPG_TRUE, null_quote, null_dequote, {0}},
>         {TINTERVALOID, "tinterval", DBDPG_TRUE, null_quote, null_dequote, {0}},
> -       {UNKNOWNOID, "unknown", DBDPG_FALSE, null_quote, null_dequote, {0}},
> +       {UNKNOWNOID, "unknown", DBDPG_FALSE, quote_varchar, null_dequote, {0}},
>         {CIRCLEOID, "circle", DBDPG_FALSE, null_quote, null_dequote, {0}},
>         {CASHOID, "money", DBDPG_TRUE, null_quote, null_dequote, {0}},
>         {MACADDROID, "MAC address", DBDPG_TRUE,
> quote_varchar,dequote_varchar, {0}},
> 
> 
> On Apr 8, 2005 4:14 PM, Brandon Metcalf <[email protected]> wrote:
> > m == [email protected] writes:
> >
> >  m> --- dbdimp.c.bak        Wed Apr  6 16:40:20 2005
> >  m> +++ dbdimp.c    Fri Apr  8 15:21:29 2005
> >  m> @@ -1415,7 +1415,7 @@
> >  m>         }
> >  m>         else if (NULL == currph->bind_type) { /* "sticky" data type */
> >  m>                 /* This is the default type, but we will honor
> >  m> defaultval if we can */
> >  m> -               currph->bind_type = pg_type_data(VARCHAROID);
> >  m> +               currph->bind_type = pg_type_data(UNKNOWNOID);
> >  m>                 if (!currph->bind_type)
> >  m>                         croak("Default type is bad!!!!???");
> >  m>         }
> >
> > Using this  results in error messages like:
> >
> >   DBD::Pg::st execute failed: ERROR:  syntax error at or near "15" at character 158
> >
> > Not sure why yet.
> >
> > --
> > Brandon
> >
> 
> --
> Vlad
> 


-- 

Vlad