/usr/share/doc/odbc-postgresql/docs/config.html is in odbc-postgresql 1:09.03.0300-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>psqlODBC Configuration Options</title>
</HEAD>
<body bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000" alink="#0000ff">
<h1>psqlODBC Configuration Options</h1>
<h2>Advanced Options 1/2 Dialog Box</h2>
<ul>
<li><b>DEFAULTS:</b> Press to this button restore the normal defaults for the
settings described below.<br /> </li>
<li><b>Disable Genetic Optimizer:</b> Automatically
turns off the backend genetic optimizer at connection time. This
is a convenience feature rather than having to type it in the connect settings.
This feature was added when we noticed the backend seemed to have
big problems optimizing some queries.<br /> </li>
<li><b>KSQO (Keyset Query Optimization):</b>
<b><em>Deprecated for 7.1+ servers.</em></b> Check this option when connecting 7.0- servers and the application seems to be suffering from the following kind of queries:<br><br>
<code>select...where (a = 1 AND b = 1 AND c = 1) OR (a=1 AND b=1 AND
c = 2)...</code><br> </li>
<li><b>Recognize Unique Indexes:</b>
Check this option.<br /> </li>
<li><b>Use Declare/Fetch:</b> If
true, the driver automatically uses declare cursor/fetch to handle
SELECT statements and keeps 100 rows in a cache. This is mostly a
great advantage, especially if you are only interested in reading and not
updating. It results in the driver not sucking down lots of memory
to buffer the entire result set. If set to false, cursors will not
be used and the driver will retrieve the entire result set. For very
large tables, this is very inefficient and may use up all the Windows memory/resources.
However, it may handle updates better since the tables are not kept open,
as they are when using cursors. This was the style of the old podbc32
driver. However, the behavior of the memory allocation is much improved
so even when not using cursors, performance should at least be better than
the old podbc32.<br /> </li>
<li><b>CommLog (C:\psqlodbc_xxxx.log):</b>
Log communications to/from the backend to that file. This is good
for debugging problems.<br /> </li>
<li><b>Parse Statements:</b> Tell the driver how to gather the information about result columns of queries. See also <em>Disallow Premature</em> and <em>ServerSide Prepare</em> options.<br>
The driver checks this option first. If disabled then it checks the Server Side Prepare option. If disabled also it checks the Disallow Premature option.<br>
If neither of them is specified the driver would execute the prepared statement prematurely when the application inquires the result columns' info.<br><br>
If this option is enabled,
the driver will parse an SQL query statement to identify the columns and
tables and gather statistics about them such as precision, nullability,
aliases, etc. It then reports this information in SQLDescribeCol,
SQLColAttributes, and SQLNumResultCols. <b>Prior to PostgreSQL 6.4,
this was the only accurate way of getting information on precision from
a query result.</b><br><br>
If the parser can not deal with a column (because it is a function
or expression, etc.), it will fallback to executing the statement which
is the old style of getting the info. The parser is fairly
sophisticated and can handle many things such as column and table aliases,
quoted identifiers, literals, joins, cross-products, etc. It can
correctly identify a function or expression column, regardless of the complexity,
but it does not attempt to determine the data type or precision of these
columns.<br /> </li>
<li><b>Cancel as FreeStmt:</b>
<br /> </li>
<li><b>MyLog (C:\mylog_xxxx.log):</b>
Log debug messages to that file. This is good
for debugging problems with the driver.<br /> </li>
<li><b>Unknown Sizes: </b>This controls
what SQLDescribeCol and SQLColAttributes will return as to precision for
character data types (varchar, text, and unknown) in a result set when
the precision is unknown. <b>This was more of a workaround for pre-6.4
versions of PostgreSQL not being able to return the defined column width
of the varchar data type</b>.<br><br>
<ul>
<li><i>Maximum</i>: Always
return the maximum precision of the data type.</li>
<li><i>Dont Know</i>: Return "Don't Know"
value and let application decide.</li>
<li><i>Longest</i>: Return
the longest string length of the column of any row. Beware of this
setting when using cursors because the cache size may not be a good representation
of the longest column in the cache.</li>
<br>
<i>MS Access</i>: Seems to handle <i>Maximum</i> setting ok, as well as all the others.<br>
<i>Borland</i>: If sizes are large and lots of columns, Borland may crash badly (it doesn't seem to handle memory allocation well)
if using <i>Maximum</i> size.
</ul><br>
<li><b>Data Type Options:</b> affects how some data types are mapped:<br /> </li>
<ul>
<li><i>Text as LongVarChar</i>:
PostgreSQL TEXT type is mapped to SQLLongVarchar, otherwise SQLVarchar.</li>
<li><i>Unknowns as LongVarChar</i>: Unknown types (arrays, etc) are mapped to SQLLongVarChar, otherwise SQLVarchar</li>
<li><i>Bools as Char</i>: Bools are mapped to SQL_CHAR, otherwise to SQL_BIT.</li>
</ul><br>
<li><b>Max Varchar</b> The maximum
precision of the Varchar and BPChar(char[x]) types. The default is 254
which actually means 255 because of the null terminator. Note, if
you set this value higher than 254, Access will not let you index on varchar
columns!<br /> </li>
<li><b>Cache Size:</b>When using
cursors, this is the row size of the tuple cache. If not using cursors,
this is how many tuples to allocate memory for at any given time.
The default is 100 rows for either case.<br /> </li>
<li><b>Max LongVarChar:</b> The maximum
precision of the LongVarChar type. The default is 4094 which actually
means 4095 with the null terminator. You can even specify (-4) for
this size, which is the odbc SQL_NO_TOTAL value.<br /> </li>
<li><b>SysTable Prefixes:</b> The
additional prefixes of table names to regard as System Tables. The
driver already treats names that begin with "pg_" as system tables.
Here you can add additional ones, such as data dictionary tables (dd_).
Separate each prefix with a semicolon (;)<br /> </li>
</ul>
<h2>Advanced Options 2/2 Dialog Box</h2>
<ul>
<li><b>ReadOnly:</b> Whether the
datasource will allow updates.<br /> </li>
<li><b>Show System Tables:</b> The
driver will treat system tables as regular tables in SQLTables. This
is good for Access so you can see system tables.<br /> </li>
<li><b>LF <-> CR/LF conversion:</b> Convert Unix style line endings to
DOS style.<br /> </li>
<li><b>Updateable Cursors:</b> Enable updateable cursor emulation in the
driver.<br /> </li>
<li><b>Bytea as LO:</b> Allow the use of bytea columns for Large Objects.
<br /> </li>
<li><b>Row Versioning:</b> Allows
applications to detect whether data has been modified by other users while
you are attempting to update a row. It also speeds the update process
since every single column does not need to be specified in the where clause
to update a row. The driver uses the "xmin" system field of PostgreSQL
to allow for row versioning. Microsoft products seem to use this
option well. See the <a "http://psqlodbc.projects.postgresql.org/faq.html">faq</a>
for details on what you need to do to your database to allow for the row
versioning feature to be used.<br /> </li>
<li><b>Disallow Premature:</b>
Mainly for 7.1 to 7.3 servers. <b><em>Server side prepare</em></b> is a more preferable option for 7.4+ servers.<br>
Tell the driver how to gather the information about result columns. See also <em>Parse Staements</em> and <em>Server Side Prepare</em> options.<br>
This is an option to compensate for the lack of a server's <em>Prepare</em> functionality.
For example, (Middleware) applications issue the following ODBC API calls.<br><br>
SQLPrepare(hstmt, "select ...", ..)<br><br>
In most cases they have to know how many fields, what kind
of fields they would return and so they would issue<br><br>
SQLNumResultCols and/or <br>
SQLDescribeCols/SQLColAttribute etc.<br><br>
The problem is how the psqlODBC driver answers the inquiry. PostgreSQL hadn't
provided the <em>Prepare</em> functionality until 7.4 and we couldn't ask the
backend about it directly.
When using Disallow Premature, the driver will get the column info as follows:<br><br>
<i>
begin;(unless in a transaction)<br>
declare cursor .. for select ...<br>
fetch backward in ..<br>
close ..<br><br>
</i>
The driver gets the field info using the fetch backward's result. The fetch
backward command returns no row but returns the field info. Though the command
is expected to be returned immediately it isn't true for 7.0- servers
unfortunately.
The 7.1 or later servers <b>do</b> seem to return from the fetch backward
command immediately.<br /> </li>
<li><b>True is -1:</b> Represent TRUE as -1 for compatibility with some applications.
<br /> </li>
<li><b>Server side prepare:</b> Applicable for 7.3+ servers and <em>recommended for 7.4+.</em><br /> 
(7.4+) Tell the driver how to gather the information about result columns. See also <em>Parse Statement</em> and <em>Disallow Premature</em> options.<br>        By using extended query protocol the driver replies to the inquiry correctly and effectively.<br> 
(7.4+) By using extended query protocol the driver replies to the inquiry for the information of parameters.<br> 
(7.3+) When using prepared statements, prepare them on the server rather than in the driver. This can give a slight performance advantage as the server<br>
        doesn't need to re-parse the statement each time it is used.<br /> </li>
<li><b>use gssapi for GSS request:</b> GSSAPI use to AUTH_REQ_GSS request from a server.(only Windows)<br /> </li>
<li><b>Int8 As:</b> Define what datatype to report int8 columns as.<br /> </li>
<li><b>Extra Opts:</b> combination of the following bits.<br /><br>
0x1: Force the output of short-length formatted connection string. Check this bit when you use MFC CDatabase class.<br />
0x2: Fake MS SQL Server so that MS Access recognizes PostgreSQL's serial type as AutoNumber type.<br />
0x4: Reply ANSI (not Unicode) char types for the inquiries from applications. Try to check this bit when your applications don't seem to be good at handling Unicode data.<br /> </li>
<li><b>Protocol:</b> Note that when using SSL connections this setting is ignored.<br />
<ul>
<li><i>6.2:</i> Forces driver to
use PostgreSQL 6.2(V0) protocol, which had different byte ordering, protocol,
and other semantics.<br />
<li><i>6.3</i>: Use the 6.3(V1) protocol. This is compatible
with both V1(6.3) and V2(6.4 to 7.3) backends.<br /> </li>
<li><i>6.4+</i>: Use the 6.4(V2) protocol. This is only compatible
with 6.4 and higher backends.<br /> </li>
<li><i>7.4+</i>: Use the 7.4(V3) protocol. This is only compatible
with 7.4 and higher backends.<br /> </li>
</ul></li>
<li><b>Level of rollback on errors:</b> Specifies what to rollback should an
error occur.<br />
<ul>
<li><i>Nop(0):</i> Don't rollback anything and let the application handle the
error.<br /> </li>
<li><i>Transaction(1):</i> Rollback the entire transaction.<br /> </li>
<li><i>Statement(2):</i> Rollback the statement.<br /> </li>
<br>
<b>Notes in a setup: This specification is set up with a PROTOCOL option parameter.</b><br><br>
PROTOCOL=[6.2|6.3|6.4|7.4][-(0|1|2)]<br>
default value is a sentence unit (it is a transaction unit before 8.0).<br>
<br>
</ul></li>
<li><b>OID Options:</b><br />
<ul>
<li><i>Show Column: </i> Includes the OID
in SQLColumns. This is good for using as a unique identifier to update
records if no good key exists OR if the key has many parts, which
blows up the backend.<br /> </li>
<li><i>Fake Index: </i> This option
fakes a unique index on OID. This is useful when there is not a real
unique index on OID and for apps which can't ask what the unique identifier
should be (i.e, Access 2.0).<br /> </li>
</ul></li>
<li><b>Connect Settings:</b> The
driver sends these commands to the backend upon a successful connection.
It sends these settings AFTER it sends the driver "Connect Settings".
Use a semi-colon (;) to separate commands. This can now handle any
query, even if it returns results. The results will be thrown away
however!<br /> </li>
</ul>
<h2>Global settings Dialog Box</h2>
<p>This dialog allows you to specify pre-connection/default logging
options</p>
<ul>
<li><b>CommLog (C:\psqlodbc_xxxx.log - Communications log):</b>
Log communications to/from the backend to that file. This is good
for debugging problems.<br /> </li>
<li><b>MyLog (C:\mylog_xxxx.log - Detailed debug output):</b>
Log debug messages to that file. This is good
for debugging problems with the driver.<br /> </li>
<li><b>MSDTCLog (C:\pgdtclog\mylog_xxxx.log - MSDTC debug output):</b>
Log debug messages to that file. This is good
for debugging problems with the MSDTC.<br /> </li>
<li><b>Specification of the holder for log outputs:</b>
Adjustment of write permission.<br /> </li>
</ul>
<h2>Manage DSN Dialog Box</h2>
<p>This dialog allows you to select which PostgreSQL ODBC driver
to use for this connection. Note that this may not work with third
party drivers.</p>
<h2>How to specify as a connection option</h2>
<p>There is a method of specifying a connection option in a keyword strings.</p>
<p>Example:VBA</p>
<ul><li><b>
myConn = "ODBC;DRIVER={PostgreSQL};" & serverConn & _
"A0=0;A1=6.4;A2=0;A3=0;A4=0;A5=0;A6=;A7=100;A8=4096;A9=0;" & _
"B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=1;" & _
"C0=0;C1=0;C2=dd_"
</b></li>
</ul>
<p>Please refer to a <a href="config-opt.html">keyword list</a> for details. </p>
</body>
</html>
|