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

Re: ODBC Performance

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: F畸io Sato <sato(at)simepar(dot)br>
Cc: Joel Burton <joel(at)joelburton(dot)com>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: ODBC Performance
Date: 2001-10-19 03:22:29
Message-ID: 3BCF9C75.2E4CE0AA@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
F畸io Sato wrote:
> 
> > > I'm using the ODBC Driver version 07_01_0007 with ADO and the performance
> > > is very disappointing... I have a procedure that update 868 rows and it is
> > > taking more than 5 minutes to complete.
> > >
> > > After some search on the mailing lists I've found similar problems but
> > > didn't find any answer to them. Can someone help me?
> >
> > Are you committing after each operation, or is the ODBC driver forcing
> > this?
> >
> > By "procedure", do you mean as PG-backend proc (in plpgsql or something
> > like that), or do you mean client-side procedure that calls PG 868 times?
> >
> > --
> >
> > Joel BURTON  |  joel(at)joelburton(dot)com  |  joelburton.com  |  aim: wjoelburton
> > Independent Knowledge Management Consultant
> 
> I think that the source code may be a better answer to your questions,
> so this is basically what I'm doing:
> 

[snip]

> 
> ' Then I open the connection and do the updates
> 
> conn.Open "DSN=mydb;uid=username;pwd=mypassword"
> 
> For I = 0 To size - 1
>   sql = "update mytable set value1 = " & array1(I) & ", value2 = " &
> array2(I) & _
>         ", value3 = " & array3(I) & ... & ", value20 = " & array20(I) &
> -
>         " where code = " & codes(I)
>   conn.Execute(sql)
> Next I
> 

First aren't you turning on ODBC trace ?
Second, how does 
  explain update mytable set value1 = .., 
                             value20 = ..
          where code = ..;
show using psql ?

regards,
Hiroshi Inoue

In response to

pgsql-odbc by date

Next:From: Eiji TokuyaDate: 2001-10-19 04:06:49
Subject: Re: Support for Special Big5 double-byte characters
Previous:From: Hiroshi InoueDate: 2001-10-18 23:56:44
Subject: Re: Support for Special Big5 double-byte characters

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