Hi Hiroshi,
Thanks for replying back so fast.
I have checked the "bytea as LO" checkbox on the second page of the datasource in odbc adminstrator. So are you
talkingabout a setting somewhere else or that one? If that one, then I still get this error with it checked.
I don't see any comments by you on the ticket itself at:
http://pgfoundry.org/tracker/index.php?func=detail&aid=1011196&group_id=1000125&atid=538
Respectfully Yours,
Michael Vitale
Arin DBA
American Registry for Internet Numbers
michaelv@arin.net
________________________________________
From: pgsql-odbc-owner@postgresql.org [pgsql-odbc-owner@postgresql.org] on behalf of Hiroshi Inoue [inoue@tpf.co.jp]
Sent: Tuesday, May 22, 2012 11:53 PM
To: Michael Vitale
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] cannot copy very large bytea data
Hi Michael,
(2012/05/22 22:57), Michael Vitale wrote:
> I am able to copy a row with a 127megabyte column, but not with one that
> is 399 megabytes.
Please try the type lo instead of bytea.
regards,
Hiroshi Inoue
> Here is the log output of the one that fails:
>
> [4272-42.487]SQL_VARBINARY: about to call convert_to_pgbinary, used =
> 399966009
> [4272-42.488]STATEMENT ERROR: func=enlarge_statement, desc='', errnum=1,
> errmsg='Query buffer allocate error in copy_statement_with_parameters'
> [4272-42.496]CONN ERROR: func=enlarge_statement, desc='', errnum=0,
> errmsg='(NULL)'
> [4272-42.499]retval=-1
> [4272-42.500][[SQLGetDiagFieldW]] Handle=(3,08F47DD0) Rec=1 Id=4
> info=(09BF6788,12)
> [4272-42.500]PGAPI_GetDiagField entering
> rec=1[4272-42.500]ER_ReturnError: status = 1, msg = #Query buffer
> allocate error in copy_statement_with_parameters#
> [4272-42.501] szSqlState = 'HY000',len=61, szError='(null)'
> [4272-42.501]PGAPI_GetDiagField exiting 0
>
--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc
