bug in postodbc

I woud like ot report a bug in Postgresql ODBC driver. I use postgresql
ver 6.3 and ODBC driver version 6.30.0250 and MS ACCESS 97. When I try
to insert backslash \ into a varchar field in linked table through MS
ACCESS it doesn't work. Error messages :

ODBC-insert on a linked table 'test' failed.

Error while executing the query;
ERROR: parser: parse error at or near "" (#1)

And a piece of psqlodbc.log

 conn=37558536, query='BEGIN'
conn=37558536, query='INSERT INTO  "test"  ("a") VALUES ('\')'
ERROR from backend during send_query: 'ERROR:  parser: parse error at or
near ""'
conn=37558536, query='ABORT'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while
executing the query'

------------------------------------------------------------
                 hdbc=37558536, stmt=37683416, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=37554272, parameters_allocated=1
                 statement_type=1, statement='INSERT INTO  "test"  ("a")
VALUES (?)'
                 stmt_with_params='INSERT INTO  "test"  ("a") VALUES
('\')'
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0,
scroll_concurrency=1
                 cursor_name='SQL_CUR023F00D8'
                 ----------------QResult Info
-------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=10, errmsg='ERROR:  parser:
parse error at or near ""'
            ------------------------------------------------------------

            henv=37553728, conn=37558536, status=1, num_stmts=16
            sock=37553744, stmts=37553792, lobj_type=-999
            ---------------- Socket Info -------------------------------

            socket=336, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=37564832, buffer_out=37568936
            buffer_filled_in=2, buffer_filled_out=0, buffer_read_in=2


Is this really a bug?


Tibor Arpas