Re: Problems with PostGreSQL and Windows 2003

Hi,

Here is a piece of psqlodbc log file:

[0.000]conn=02DE3A70, PGAPI_DriverConnect(
in)='DSN=BI;UID=biuser;PWD=xxxxxxxxx;', fDriverCompletion=0
[0.000]DSN info:
DSN='BI',server='localhost',port='5432',dbase='BI',user='biuser',passwd='xxxxx'
[0.000]
onlyread='0',protocol='7.4',showoid='0',fakeoidindex='0',showsystable='0'
[0.000] conn_settings='',conn_encoding='(null)'
[0.000] translation_dll='',translation_option=''
[0.000]Driver Version='08.02.0400,200704270001' linking static Multithread library
[0.000]Global Options: fetch=100, socket=4096, unknown_sizes=0,
max_varchar_size=255, max_longvarchar_size=8190
[0.000] disable_optimizer=0, ksqo=1, unique_index=1,
use_declarefetch=1
[0.000] text_as_longvarchar=1, unknowns_as_longvarchar=0,
bools_as_char=1 NAMEDATALEN=64
[0.000] extra_systable_prefixes='dd_;', conn_settings=''
conn_encoding=''
[0.046] [ PostgreSQL version string = '8.2.5' ]
[0.046] [ PostgreSQL version number = '8.2' ]
[0.046]conn=02DE3A70, query='select oid, typbasetype from pg_type where typname
= 'lo''
[0.046]NOTICE from backend during send_query: 'SLOG'
[0.046]NOTICE from backend during send_query: 'C00000'
[0.046]NOTICE from backend during send_query: 'Mstatement: select oid,
typbasetype from pg_type where typname = 'lo''
[0.046]NOTICE from backend during send_query: 'Fpostgres.c'
[0.046]NOTICE from backend during send_query: 'L811'
[0.046]NOTICE from backend during send_query: 'Rexec_simple_query'
[0.046] [ fetched 1 rows ]
[0.046] [ Large Object oid = 17288 ]
[0.046] [ Client encoding = 'LATIN9' (code = 16) ]
[0.046]conn=02DE3A70,
PGAPI_DriverConnect(out)='DSN=BI;DATABASE=BI;SERVER=localhost;PORT=5432;UID=biuser;PWD=xxxxxxxxx;SSLmode=disable;ReadOnly=0;Protocol=7.4-1;FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVarcharSize=255;MaxLongVarcharSize=8190;Debug=0;CommLog=1;Optimizer=0;Ksqo=1;UseDeclareFetch=1;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;;LFConversion=1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;UseServerSidePrepare=0;LowerCaseIdentifier=0;XaOpt=1'
[0.062]STATEMENT ERROR: func=set_statement_option, desc='', errnum=30,
errmsg='The option may be for MS SQL Server(Set)'
[0.062]
------------------------------------------------------------
[0.062] hdbc=02DE3A70, stmt=02DE85C8, result=00000000
[0.062] prepare=0, internal=0
[0.062] bindings=00000000, bindings_allocated=0
[0.062] parameters=02DE8F48, parameters_allocated=1
[0.062] statement_type=-2, statement='(NULL)'
[0.062] stmt_with_params='(NULL)'
[0.062] data_at_exec=-1, current_exec_param=-1, put_data=0
[0.062] currTuple=-1, current_col=-1, lobj_fd=-1
[0.062] maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0,
scroll_concurrency=1
[0.062] cursor_name=''
[0.062] ----------------QResult Info
-------------------------------
[0.062]CONN ERROR: func=set_statement_option, desc='', errnum=0, errmsg='(NULL)'
[0.062]

Thanks,
Cláudia.

> On Sun, Nov 25, 2007 at 10:38:31AM -0200, claudia(dot)amorim(at)pcinformatica(dot)com(dot)br
> wrote:
>> Hello,
>>
>> I changeded shared buffers to 256 MB. But I still receiving the error message.
>> So I changed to 128 MB, and I received the error again.
>> I'm using a cursor via ODBC.
>
> Are you using a cursor, because it certainly doesn't look like you're
> using a cursor, just a plain select. Which probably means youre client
> side is running out of memory.
>
> So, check you're using a cursor. Or just limit the output to however
> many rows you actually want.
>
> Have a nice day,
> --
> Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
>> Those who make peaceful revolution impossible will make violent revolution
>> inevitable.
>> -- John F Kennedy
>