Hi,

When i use DTS from mssql to export data to postgres and the table is
> 1million i get an error: Out of memory while reading tuples.
I'm trying to understand the issue so i changed
log_min_duration_statement=3D-1 in postgresql.conf to get all statements
executed and i get
BEGIN; INSERT one row sent from the dts RETURNING ctid; SELECT WHERE
ctid; COMMIT;

and when i select count(*) from table i get the rows it migrated until
now... so, obviously the psqlODBC should be free'ing the memory it
used for that tuple but instead when i see the Task Manager in windows
i see how the memory is going down until it gets to zero...

so this should be a memory leak, no? how can i trace it in the psqlODBC?

--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitaci=C3=B3n de PostgreSQL

--
Sent via pgsql-odbc mailing list (pgsql-odbc [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Jaime Casanova wrote:
> Hi,
>
> When i use DTS from mssql to export data to postgres and the table is
>> 1million i get an error: Out of memory while reading tuples.
> I'm trying to understand the issue so i changed
> log_min_duration_statement=-1 in postgresql.conf to get all statements
> executed and i get
> BEGIN; INSERT one row sent from the dts RETURNING ctid; SELECT WHERE
> ctid; COMMIT;
>
> and when i select count(*) from table i get the rows it migrated until
> now... so, obviously the psqlODBC should be free'ing the memory it
> used for that tuple but instead when i see the Task Manager in windows
> i see how the memory is going down until it gets to zero...
>
> so this should be a memory leak, no? how can i trace it in the psqlODBC?

Could you please try the drivers on testing for 8.4.0201 at
http://www.geocities.jp/inocchichichi/psqlodbc/index.html
?

regards,
Hiroshi Inoue


--
Sent via pgsql-odbc mailing list (pgsql-odbc [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

On Thu, May 20, 2010 at 10:19 PM, Hiroshi Inoue <inoue [at] tpf.co.jp> wrote:
> Jaime Casanova wrote:
>>
>>
>> so this should be a memory leak, no? how can i trace it in the psqlODBC?
>
> Could you please try the drivers on testing for 8.4.0201 at
> =C2=A0http://www.geocities.jp/inocchichichi/psqlodbc/index.h tml
> ?
>

seems like this fix the problem

--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitaci=C3=B3n de PostgreSQL

--
Sent via pgsql-odbc mailing list (pgsql-odbc [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

On Sat, May 22, 2010 at 7:35 AM, Jaime Casanova <jaime [at] 2ndquadrant.com> wro=
te:
> On Thu, May 20, 2010 at 10:19 PM, Hiroshi Inoue <inoue [at] tpf.co.jp> wrote:
>> Jaime Casanova wrote:
>>>
>>>
>>> so this should be a memory leak, no? how can i trace it in the psqlODBC?
>>
>> Could you please try the drivers on testing for 8.4.0201 at
>> =C2=A0http://www.geocities.jp/inocchichichi/psqlodbc/index.h tml
>> ?
>>
>
> seems like this fix the problem
>

When will this be released?

--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitaci=C3=B3n de PostgreSQL

--
Sent via pgsql-odbc mailing list (pgsql-odbc [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc