Help with hang on empty query (PG 7.3.2, psqlodbc-07.03.0200)

Поиск
Список
Период
Сортировка
От Steve Wampler
Тема Help with hang on empty query (PG 7.3.2, psqlodbc-07.03.0200)
Дата
Msg-id 1068221099.12206.14.camel@weaver.tuc.noao.edu
обсуждение исходный текст
Ответы Re: Help with hang on empty query (PG 7.3.2, psqlodbc-07.03.0200)  (Jeff Eckermann <jeff_eckermann@yahoo.com>)
Re: Help with hang on empty query (PG 7.3.2,  (Steve Wampler <swampler@noao.edu>)
Список pgsql-odbc
I recently upgraded a system from RedHat 8 to RedHat 9, which
meant an upgrade of PG 7.2 to 7.3.2.  Several applications
that are written in a language that relies upon odbc to access
postgresql have stopped working.

I've installed from source psqlodbc-07.03.0200 (pthread
and iodbc support).  From the logs it looks as though the
connection is succeeding up to the point that an
empty query is sent (dunno why the empty query is being
sent - it appears to be part of the connection procedure).
At this point the connection hangs - no messages, or errors.
Killing the client program causes postgresql to log a:

   LOG:  pq_recvbuf: unexpected EOF on client connection

message.

These programs had all been working with the odbc RPM that was
available for 7.2.3, so I assume it's something to do with
how I configured the build.

(Can someone tell me why the odbc RPM was dropped with 7.3?)

Thanks for any help!

Various logs and traces:

odbc.trace:

   SQLAllocEnv ( ... )
   SQL_SUCCESS

   SQLAllocConnect ( ... )
   SQL_SUCCESS

   SQLConnect ( ... )

psqlodbc_swampler17169.log:

   conn = 135226032, PGAPI_Connect(DSN='swampler', UID='swampler',
         PWD='xxxxx')
   Global Options: Version='07.03.0200', fetch=100, socket=4096,
         unknown_sizes=0, max_varchar_size=254,
          max_longvarchar_size=8190
                disable_optimizer=1, ksqo=1, unique_index=1,
                          use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0,
                          bools_as_char=1 NAMEDATALEN=64
                extra_systable_prefixes='dd_;', conn_settings=''
                         conn_encoding='OTHER'
                conn=135226032, query=' '

mylog_swampler17169.log:

    [1075229312]CC_connect: entering...
    [1075229312]CC_connect(): DSN = 'swampler', server = 'weaver',
           port = '5432', database = 'swampler', username = 'swampler',
           password='xxxxx'
    [1075229312]connecting to the server socket...
    [1075229312]connection to the server socket succeeded.
    [1075229312]sizeof startup packet = 292
    [1075229312]sent the authentication block.
    [1075229312]sent the authentication block successfully.
    [1075229312]gonna do authentication
    [1075229312]read 15, global_socket_buffersize=4096
    [1075229312]auth got 'R'
    [1075229312]areq = 0
    [1075229312]auth got 'K'
    [1075229312]auth got 'Z'
    [1075229312]sending an empty query...
    [1075229312]send_query(): conn=135226032, query=' '

--
Steve Wampler -- swampler@noao.edu
Quantum materiae materietur marmota monax si marmota
                    monax materiam possit materiari?

В списке pgsql-odbc по дате отправления:

Предыдущее
От: Jeff Eckermann
Дата:
Сообщение: Re: Access, pass-through queries and isolation level
Следующее
От: "Philippe Lang"
Дата:
Сообщение: Re: Access, pass-through queries and isolation level