Bug 366431

Summary: unixODBC connection error with postgres when client_min_messages set to debug5, debug4 or debug3
Product: Red Hat Enterprise Linux 5 Reporter: Prosenjit Biswas <pbiswas>
Component: unixODBCAssignee: Tom Lane <tgl>
Status: CLOSED NEXTRELEASE QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 5.0CC: asharma, hhorak, rranade
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-19 15:34:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ODBC.INI file
none
odbcinst.ini file none

Description Prosenjit Biswas 2007-11-05 08:03:15 UTC 
Description of problem:
In the configuration file of postgresql, postgresql.conf, if the
client_min_messages set to debug5, debug4 or debug3 then unixODBC throws error
message "Failed to SQLTables" while checking it via DataManager or if they check
it via isql they got the error message "[01000][unixODBC]DEBUG:  name: unnamed;
blockState: STARTED; state: INPROGR, xid/subid/cid: 777/1/0, nestlvl: 1,
children:[ISQL]ERROR: Could not SQLTables".

For all other (debug2, debug1, notice, error, log, warning) configuration, it
works fine. 

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1.Install unixODBC and postgresql 
2. Configure /etc/odbc.ini and /etc/odbcinst.ini
3. Configure postgresql and set the "client_min_messages set = debug5" in
postgresql.conf file. 
4. Create a Database.
5. Test the connectivity via DataManager or isql.
  
Actual results:
Throws error message for querying sql tables. Failed to SQLTables. 

Expected results:
It should properly access the database and show the tables. 

Additional info:
when there is a activity from the clinet, to debug any error, client can ask for
the debug level 5. For development environments, can be asked by the customer.
Comment 1 Tom Lane 2007-11-05 13:09:12 UTC 
This report has no more information than you previously gave by email.  What is the unixODBC version?
Which Postgres ODBC driver are you using, and what's the version of that?  What's the full contents of the
two ODBC configuration files?
Comment 2 Prosenjit Biswas 2007-11-22 13:29:30 UTC 
Created attachment 266851 [details]
ODBC.INI file 

The odbc.ini file has attached.
Comment 3 Prosenjit Biswas 2007-11-22 13:31:52 UTC 
Created attachment 266861 [details]
odbcinst.ini file 

odbcinst.ini file
Comment 4 Prosenjit Biswas 2007-11-22 13:35:52 UTC 
(In reply to comment #1)
> This report has no more information than you previously gave by email.  What
is the unixODBC version?
> Which Postgres ODBC driver are you using, and what's the version of that? 
What's the full contents of the
> two ODBC configuration files?

Unix ODBC Version
unixODBC-2.2.11-7.1  -- both 32 bit and 64 bit
unixODBC-2.2.12-1.el5s2  -- both 32 bit and 64 bit

Postgresql ODBC version
postgresql-odbc-08.01.0200-3.1
Comment 6 Tom Lane 2013-03-19 15:34:44 UTC 
RHEL-5 has now reached production phase 2, in which only security and other critical bugs will be addressed.  This is neither, so I'm afraid it won't be fixed in RHEL-5.  I believe the issue has been addressed in the newer postgresql-odbc code in RHEL-6.  (Also, RHEL-5 users might be able to migrate to unixODBC64 and postgresql-odbc64, which should resolve the problem as well.)